Re: Managing the classpath

2010-07-02 Thread Brian Schlining
> > http:// > > > forums.sun.com/thread.jspa?threadID=300557&start=0&tstart=0 > > > > > Using a classloader manually is sub-optimal because the rest of > > > Clojure, which doesn't know anything about the user-created > > > classloader, wouldn't use it to load classes; you'd have to use the > > > r

Re: Managing the classpath

2010-07-02 Thread Alessio Stalla
On Jul 2, 5:20 am, Brian Schlining wrote: > > > There's URLClassLoader for loading classes at runtime. Javadocs are > > athttp://java.sun.com/javase/6/docs/api/java/net/URLClassLoader.html. > > There's > > > an old thread about using it athttp:// > > forums.sun.com/thread.jspa?threadID=300557&star

Re: Managing the classpath

2010-07-01 Thread Brian Schlining
> > > > There's URLClassLoader for loading classes at runtime. Javadocs are > athttp://java.sun.com/javase/6/docs/api/java/net/URLClassLoader.html. > There's > > an old thread about using it athttp:// > forums.sun.com/thread.jspa?threadID=300557&start=0&tstart=0 > > Using a classloader manually is

Re: Managing the classpath

2010-07-01 Thread Steve
On Jul 1, 11:11 pm, Paul Moore wrote: > > Where I struggle is with the practicalities of managing the classpath. > From what I can tell, there is no way of modifying the classpath from > a running Java/Clojure program (barring use of a custom classloader > which sounds like deep magic). So, assumi

Re: Managing the classpath

2010-07-01 Thread Alessio Stalla
On 1 Lug, 17:47, Brian Schlining wrote: > > Where I struggle is with the practicalities of managing the classpath. > > From what I can tell, there is no way of modifying the classpath from > > a running Java/Clojure program (barring use of a custom classloader > > which sounds like deep magic). >

Re: Managing the classpath

2010-07-01 Thread j-g-faustus
On Jul 1, 4:49 pm, Paul Moore wrote: > (My biggest concern about an uberjar is that I end up with each app > having a separate bundled copy of all its dependencies. That makes > version management a huge pain - imagine a bugfix release of > clojure.jar - but is otherwise not an unreasonable option

Re: Managing the classpath

2010-07-01 Thread Luc Préfontaine
We have over 130 jar dependencies on our classpath and performance is not an issue. After the classes you are using are loaded at least once, there are no significant impacts. Each app refers to the same shared lib folder so we update a single jar and get every app gets the update after a restart

Re: Managing the classpath

2010-07-01 Thread Paul Moore
On 1 July 2010 16:49, Kevin Livingston wrote: > Some of the build tools like Maven can help a lot. (Thanks for your other comments, which I've cut. But this one made me think). I've heard comments like this elsewhere (with regard to both Maven and Leiningen), but I'm not quite sure I follow. You

Re: Managing the classpath

2010-07-01 Thread Paul Moore
On 1 July 2010 15:29, Laurent PETIT wrote: > Hello, > > note that with java 6 you can specify at once to add all the jars > located in a directory: > > java -cp "libs/*" clojure.main > > and you can place any jar you want in directory libs. > > and this is composable: > > java -cp "clojure.jar:lib

Re: Managing the classpath

2010-07-01 Thread Kevin Livingston
> If you have a directory containing Clojure a source code tree for LibA > on the classpath for ProjB then you should be able to replace the > files without changing any classpath. right, I've just been trying to figure out how to do that in Maven when LibA and ProjB are separate projects (with se

Re: Managing the classpath

2010-07-01 Thread Daniel Gagnon
That's really convenient to know! I just symlinked clojure.jar to /usr/share/java where all the java jars are on k/ubuntu and now I just have to have those two lines in my .bashrc file: export CLASSPATH=.:/usr/share/java/* alias clj="rlwrap java clojure.main" On Thu, Jul 1, 2010 at 10:29 AM, Laur

Re: Managing the classpath

2010-07-01 Thread Michael Wood
On 1 July 2010 17:49, Kevin Livingston wrote: > Some of the build tools like Maven can help a lot. > > However, one different/related issue I have is when I have multiple > projects I am developing, say a library, LibA, and a project that uses > it ProjB, if I want to co-develop them, it can get a

Re: Managing the classpath

2010-07-01 Thread Kevin Livingston
Some of the build tools like Maven can help a lot. However, one different/related issue I have is when I have multiple projects I am developing, say a library, LibA, and a project that uses it ProjB, if I want to co-develop them, it can get a little hairy, and I haven't figured out the solution...

Re: Managing the classpath

2010-07-01 Thread Brian Schlining
> > > > Where I struggle is with the practicalities of managing the classpath. > From what I can tell, there is no way of modifying the classpath from > a running Java/Clojure program (barring use of a custom classloader > which sounds like deep magic). > There's URLClassLoader for loading classes

Re: Managing the classpath

2010-07-01 Thread Luc Préfontaine
Yep, we have been using this for a year or so and this solves the classpath/jar file location issue nicely. Hence the usefulness of CLOJURE_HOME and alikes to locate this single folder from a very simple wrapper script... Luc P. Sent from my iPod On 2010-07-01, at 10:29, Laurent PETIT wrote:

Re: Managing the classpath

2010-07-01 Thread Laurent PETIT
Hello, note that with java 6 you can specify at once to add all the jars located in a directory: java -cp "libs/*" clojure.main and you can place any jar you want in directory libs. and this is composable: java -cp "clojure.jar:libs/*" clojure.main My 0.02€, just in case you didn't know this