John Griessen wrote:
So, my question to you all is:
Is it better to copy or move the generated classes directory tree contents to
your basic /usr/local/classes directory so as to have shorter classpath=
environment variables, or is it somehow preferable to have a long classpath=
pointing to many of the .jar files generated? Each is going to have a
compile step. Each is likely to require a copy from the build dir to
the dirs on the classpath.
Do you all prefer to just put the build dirs
of code you are changing on your classpath? The tutorials on classpath say
to avoid confusion and keep them short or use jwhich and such tools to sort
out confusion...
I would put the build dirs on the class path (I would actually tend
to merge the two source trees if I was planning on doing lots of work
assuming they are in different packages they don't get too mixed up).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
