Add support for arbitrary class paths about leiningen

[technomancy]

I'm unlikely to implement this myself since I'm not convinced of the reasoning. (If you use proprietary jars that aren't in any public maven repos, you should put them in private maven repos. It's a bit more work up front, but it will pay off.) But I would certainly accept a patch that implemented it cleanly.

[rosejn]

I would like this feature so that I can use git submodules in a project and automatically add the submodule src directories to the classpath. Currently I'm not sure how to setup leiningen with submodules without something that lets me add to the classpath. I'll post on the group, but it seems like exactly this feature would do the trick.

[RickMoynihan]

The problem with putting jars in private maven repo's, is that when there's a dozen or so jar files, it becomes a pain... Especially when I have to tell every developer on the project to install them into a private maven repo. This is error prone (though admitedly I could create a script to do it).

I realise that I could probably setup a server acting as a maven repo or something, but this is fragile to developers working remotely (as I don't want to have to setup a server accessible to the internet).

I've heard people mention that clojure does something funky with classloaders (which prevents it being used with for example OSGI)... How are Clojure's classloaders structured and would it be an impedement to retroactively loading classes in the system classloader?

[technomancy]

The problem with putting jars in private maven repo's, is that when there's a dozen or so jar files, it becomes a pain... Especially when I have to tell every developer on the project to install them into a private maven repo.

I don't think you understand; I'm not talking about a local maven repo, I'm talking about one that's shared among all developers on the project, but requires a password to access. That way you know that everyone's always working from the exact same versions.

Anyway, I will take a patch for this if someone decides to implement it.

[technomancy]

This is actually covered pretty well by the checkout dependencies feature. I'll be sure it's documented for the release.