Does anyone think that this is the wrong behavior and that the classloader shouldn't look in the parent classloader first ?
BTW reading the documentation, it seems that build.sysclasspath should control this bevaior, but I can't seem to make it work. Any 3rdparty task that uses javax.transform.* is pretty much hosed since jaxp.jar contains these classes so you bump up to the parent classloader and then you are in %ANT_HOME%\lib hell. The only way around it I could find was to remove java.transform.* from jaxp.jar (pretty sick). It would be nice if Ant could bootstrap from the system classpath then never need it again, having a DOS bat script that recursively adds jars to the classpath isn't the way I'd like to manage the classpath. Basically I'd like to be able to just take a standard Ant release with just ant.jar jaxp.jar & crimson.jar then use my own Ant managed classpaths for *everything* else, optional tasks included (and be able to have xerces.jar in my taskdef classpath if I need to or whatever) Am I way off track ? Cheers, Matthew > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 21, 2001 7:05 PM > To: [EMAIL PROTECTED] > Subject: Re: taskdef'ing junit > > > On Sun, 18 Nov 2001, Peter Donald <[EMAIL PROTECTED]> wrote: > > > So you will have to remove optional.jar from ${ant.home}/lib if you > > want to taskdef junit. > > Or remove the JUnit task classes from there and leave the rest in > optional.jar (just to do the same again when you want to use <style> > without adding Xalan to ANT_HOME/lib or <script> without adding Rhino > or ...) > > Stefan > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
