ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: Class-Path entry in the manifest.mf of ant.jar
Date Wed, 29 Jan 2003 19:10:12 GMT
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:steve_l@iseran.com] 
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" <Darin_Swanson@oti.com>
To: <ant-dev@jakarta.apache.org>
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: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org


Mime
View raw message