LinkageError

[James Sadler <ja...@eb2.com>]

Hi All,

I am on a mission trying to make my company's integration build go 
faster.  We have loads of tests to run and currently the only way they 
will run is when maven.junit.fork = true.

If we don't do this, we get the XML-related LinkageError.  I have been 
reading this mailing list, but the 'solution' is always to TURN ON 
forking - which doesn't really cut it at the moment.  Forking makes the 
tests slow, which is not ideal.

We are using Maven 1.0.2 and have no plans to upgrade (unless this bug 
is definitely fixed in a later version!).

I have tried copying the test:test goal from the test plugin into one of 
our maven.xml files and played around with the Jelly script that 
controls whether or not the xml jars are included on the classpath 
depending on whether or not forking is switched on but with no luck.

Can somebody with a deep understanding of this problem help me with some 
answers?  I have been on a wild goose chase on this for a couple of days 
now...

Thanks for any help you can give,

James.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: LinkageError

[Brett Porter <br...@gmail.com>]

Maven 1.1 beta 2 is mostly backwards compatible and significantly
faster in general. For tests, not forking probably works (as it uses
the bundled JDK parser instead of an endorsed xerces), but even if not
it offers "forkmode=once" support for tests meaning all the benefits
of forking without the performance hit.

Cheers,
Brett

On 11/2/05, James Sadler <ja...@eb2.com> wrote:
>
> Hi All,
>
> I am on a mission trying to make my company's integration build go
> faster.  We have loads of tests to run and currently the only way they
> will run is when maven.junit.fork = true.
>
> If we don't do this, we get the XML-related LinkageError.  I have been
> reading this mailing list, but the 'solution' is always to TURN ON
> forking - which doesn't really cut it at the moment.  Forking makes the
> tests slow, which is not ideal.
>
> We are using Maven 1.0.2 and have no plans to upgrade (unless this bug
> is definitely fixed in a later version!).
>
> I have tried copying the test:test goal from the test plugin into one of
> our maven.xml files and played around with the Jelly script that
> controls whether or not the xml jars are included on the classpath
> depending on whether or not forking is switched on but with no luck.
>
> Can somebody with a deep understanding of this problem help me with some
> answers?  I have been on a wild goose chase on this for a couple of days
> now...
>
> Thanks for any help you can give,
>
> James.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org