Actually, with the addClasspathEntry() method used to pull in ant.jar and junit.jar, a few other such calls for key classes in these other JARs could do the job as well it seems to me.
I vaguely remember discussions about pulling those entries out of ant.jar's manifest, and having an empty JAR with them defined!?!? Is that in 1.6? --DD -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 29, 2003 12:30 PM To: Ant Developers List; Darin Swanson Subject: Re: Class-Path entry in the manifest.mf of ant.jar try running a forked <junit> without them :) ----- Original Message ----- From: "Darin Swanson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 29, 2003 09:18 Subject: Class-Path entry in the manifest.mf of ant.jar In the Ant 1.5.1 distribution, the ant.jar has a Manifest.mf file that contains the following entry: Class-Path: xml-apis.jar xercesImpl.jar optional.jar xalan.jar. I am working on the Ant integration for the Eclipse project and this entry is causing us some problems to do with classloading (specifically excluding optional.jar from the classpath if the user has indicated to do so). I am interested in the reason for these entries? Thanks for your time Darins --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
