commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <sco...@javactivity.org>
Subject Re: commons projects and maven
Date Wed, 21 Apr 2004 11:49:12 GMT
I no longer have the output, but my sense of the matter is the same as Mark's.
The 'culprit' is j-coverage.

On Tuesday 20 April 2004 11:34 pm, Phil Steitz wrote:
> Mark R. Diggory wrote:
> > Steve Cohen wrote:
> >> I wish I understood what the heck it was doing.  It does too much.
> >> I notice that it runs the unit tests twice.  Why?
> >
> > Can you attach the output? This would help me determine where its
> > happening twice.
>
> I may be wrong, but I suspect that the tests running twice is due to the
> j-coverage plugin running the tests to generate the coverage report (like
> clover does) in addition to the test run kicked off by the build element.
>   That's what I always see when I ask for clover reports.  It would be
> cool if maven could pick this up and just run the tests once.
>
> Phil
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message