ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: Crimson hard coded into junit
Date Wed, 01 May 2002 22:30:37 GMT

----- Original Message -----
From: "Jeff Tulley" <>
To: <>
Sent: Wednesday, May 01, 2002 12:35 PM
Subject: Re: Crimson hard coded into junit

> I had this exact exception happen on my home machine, and I am pretty
> darn sure that I do not have j2ee.jar in my classpath.  I eventually
> went with junit.fork=true, and live with it being slower.  I was going
> to give you all some feedback for documentation improvements in this
> area (at very least), but work got too busy for me.

usually startup hit is negligble once the JVM is in memory, especially if
you have enough ram

> I think there still might be a crimson / xerces problem here, since
> what I was doing was running a test that used xerces(I think), and junit
> was wanting crimson.  I also had versioning problems on my machine - at
> least two different xerces.
> With the information that you have given about it being a classpath API
> clash(I figured as much), I'll re-run this at home and see if there is
> anything that can be determined and / or fixed.

hey, I am not the only one. It looks like a defect to me; the classpath of
the junit tests affecting how ant runs itself.

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

View raw message