> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED] > Sent: Thursday, 25 January 2001 10:47 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: cvs commit: jakarta-ant build.bat > > > At 01:51 24/1/01 -0000, [EMAIL PROTECTED] wrote: > >conor 01/01/24 05:51:57 > > > > Modified: . build.bat > > Log: > > Fix typo on classpath > > Include system class path so optional packages can be found. > > I actually tried to avoid this as it introduces risk ()ie no longer know > exactly what is included in build process) and it means that you can no > longer just type build.[sh|bat] because CLASSPATH is undefined > and will not > work. > > So perhaps it would be better to test if CLASSPATH is set ? >
Not sure what your issue is here. It works fine for me with a classpath that was not set 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
