----- Original Message ----- From: "Peter Donald" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, December 14, 2000 6:19 PM Subject: Re: Default libs included
> At 05:12 14/12/00 -0000, Steve Loughran wrote: > > > >Set up ANTLIBPATH with "c:\java\lib\*.jar;.\lib\*.jar" and we could get the > >effect without having to hardcode so many assumptions into the scripts. > > This just means you have to have a script file that sets ANTLIBPATH instead > of going "export CLASSPATH=`echo lib/*.jar | tr ' ' ':'`". Each means that > a script file is necessary ;( not if the special ANTLIBPATH variable is wildcarded; the expansion would get done in the normal script. <diversion duration="short"> Isn't it funny how Java adds some of the most sophisticated run time introspection and class manipulation of modern languages, and then drops the whole concept on the floor with the whole classpath environment thing. </diversion> The ideal place to put the declaration of which libraries to include in ant, above and beyond the core, is of course the build.xml file itself. That should be possible with a custom classloader, and could be a nice substitue for hacking the invocation scripts. -steve
