Weird - I switched from Java5 to the 1.4.2_10 JDK and everything is now
building fine. I'll try again with J5 later to see if that reproduces
the problem.
Spooky.
Incidentally, if I haven't already said this, three cheers for the
automated builds, David!
--G
David Illsley wrote:
Glen,
Just FYI,the m2 build (including tests) is currently passing on
continuum (includes jaxws). [1]
David
[1]
http://ws.zones.apache.org:10000/continuum/servlet/continuum/target/ProjectBuilds.vm/view/ProjectBuilds/id/61;jsessionid=32deio4w3ssw4
On 13/03/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Nicholas L Gallardo wrote:
> That's interesting... I haven't seen that one before myself, but I
know
> others have seen OOM errors when trying to run the JAXWS test suite
with
> trace enabled. The other interesting bit is that the elapsed time
for the
I'm running a clean build, so whatever's the defaults, I'm using them.
Have you tried the Maven2 build? I just tried it again after wiping my
entire repository, and still get the same exact errors.
The Maven1 build works fine for the JAXWS module.
Any clues greatly appreciated.
> tests is over double what the normal run is. I'm not familiar with
> surefire so I can't comment on what overhead that might be adding. Is
> there an additional tool that's needed to run that, or is it
packaged with
> maven by default?
I assumed it's what Maven2 does by default to run tests...?
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
