ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: Removing Class-Path from Ant's own manifest
Date Wed, 02 Oct 2002 15:41:34 GMT

----- Original Message -----
From: "Stefan Bodewig" <bodewig@apache.org>
To: <ant-dev@jakarta.apache.org>
Sent: Tuesday, October 01, 2002 11:21 PM
Subject: Removing Class-Path from Ant's own manifest


> 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.
>
> 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
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6019> which is only
> fixed because Ant now ships the parser that the original reporter
> needed for his tests.
>

I dont know what the consequences will be. I remember changing the parser
named in the manifest for a 1.5 beta/RC release as it still had crimson and
I couldnt run <junit> with xml output.

Why not try it and see what happens?


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message