ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject Re: Removing Class-Path from Ant's own manifest
Date Wed, 02 Oct 2002 06:34:37 GMT
Stefan Bodewig wrote:

> Traditionally Ant's manifest includes a Class-Path entry for the XML
> parser we ship, but do we really need that?
> I know the idea was that "java -jar ant.jar" could start Ant, but that
> doesn't work anyway and we currently highly recommend to use the
> wrapper scripts we ship.

AFAIK - it does work very well ( at least I use it from time to time and 
never had problems - that's how I run ant on windows, and I just checked
on linux  ).

I agree Class-Path creates problems sometimes, as it's not as easy to
control as CLASSPATH env - so I'm +1. 

Would you mind a separate jar ( like ant-run.jar or bootstrap.jar )
in bin, with only the Class-Path manifest ? This way ant.jar will
be clean, but it'll still be possible to run ant without setting
any CLASSPATH and without scripts. Probably not a big deal, I don't
think we are too many using this feature.

> The downside of having this entry is that it is a serious problem for
> people who want to use a different XML parser in the unit tests (and
> probably in different situations as well).  See Detlef Brendle's post
> of yesterday or
> <> which is only
> fixed because Ant now ships the parser that the original reporter
> needed for his tests.

Removing the file from ant/lib could resolve the problem. 


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message