ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: DO NOT REPLY [Bug 6019] - Classpath string in the manifest for ant.jar causes problems with Junit task
Date Thu, 06 Jun 2002 17:28:21 GMT

----- Original Message -----
From: "Conor MacNeill" <conor@cortexebusiness.com.au>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Sent: Wednesday, June 05, 2002 11:36 PM
Subject: Re: DO NOT REPLY [Bug 6019] - Classpath string in the manifest for
ant.jar causes problems with Junit task


> bugzilla@apache.org wrote:
> > ------- Additional Comments From stevel@apache.org  2002-06-06
06:18 -------
> > *** Bug 8794 has been marked as a duplicate of this bug. ***
> >
>
>
> I don't believe this is correct (that they are duplicates).

You are right, but I linked them because they were both symptoms of the same
problem, manifests and XML parsers

> Bug6019 complains because the ant jars pull in the XML parser
> Bug8794 complains because the ant jars do not pull in the XML parser
>
> The latter arose because we changed from Crimson to Xerces whilst the
> former really would only be solved by not including any of the XML
> related jars in the manifest's classpath attribute.
>
> Actually I too think Ant's manifest should not include the particular
> XML jars that come bundled with Ant. Ant does not depend directly on the
> particular parser it is bundled with - it just requires a JAXP capable
> parser. Too late to change now, I guess, so 6019 should be marked as a
> WONTFIX for backward compatability reasons.

Do we need to state what parsers we require in the manifest at all, given
that ant.bat sets it up?

How do we ensure that the XmlResultFormatter of junit can generate XML, even
when fork=true? Do it DOM-less?

-steve





--
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