At 12:04 25/1/01 +1100, Conor MacNeill wrote: >Not sure what your issue is here. It works fine for me with a classpath that >was not set
Must be compiler dependent. For instance if you create something like set CLASSPATH= set LOCALCLASSPATH=foo.jar;%CLASSPATH%;junit.jar echo LOCALCLASSPATH=%LOCALCLASSPATH% would echo "LOCALCLASSPATH=foo.jar;;junit.jar" which would mean that certain tools would stop at the ;; entry. So they would only see foo.jar. Other tools would completely flake out and see nothing. Either jikes or 1.3 javac (or both) breaks the build process if CLASSPATH hasn't been set which is why I have always had to have an extra bat file that bootstraps the bootstrap process ;) > >A fixed, predetermined classpath is nice for builds but is not compatible >with the building of optional classes. The tests for the presence of >required third party classes are all guaranteed to fail if you don't use the >system classpath. As it stands now, bootstrap uses a defined classpath but >build does not. > >Conor > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
