I'm now seeing the tests run twice under cobertura (once silently, which is
a bit sneaky :) This is standalone, so that could be the reason for the
corruption you get if it conflicts with the other run.

As for cobertura and surefire report running tests again as part of the
site, even after install - yes, that always happens. It's a known issue that
requires some optimizations in the Maven lifecycle.

Plugins really don't interact directly. Everything is driven via the
lifecycle bindings, with the project object holding any information that
might change.

- Brett

On 2/22/06, David Sag <[EMAIL PROTECTED]> wrote:
>
>
> For some reason as of today the unit tests in one of my projects are now
> running 3 times when i do mvn install site.
>
> I declare the surefire plugin in my build as per normal and in my
> reporting as per normal so am not sure why this could be.
>
> I also generate pmd, cobertura, findbugs and qalab reports - all that has
> changed is i now have cobertura working.  could the cobertura reporting
> plugin be running the tests again separately to surefire?
>
> When the surefire report runs (this only runs once) i am now getting a
> 'failure to parse file at [[snipped]]/surefire-reports/TEST-
> org.epo....FopTransformerTest.xml and sure enough when i look at that file
> it ends unexpectedly at <property value=" on line 4
>
> but
>
> if i mvn clean then mvn install, the tests run once and the xml file is
> okay.  if i then as a separate task run mvn site the tests still appear to
> run 3 times but the xml file remains uncorrupted.
>
> so my questions.
>
> 1) why does surefire run the tests more than once.  surely the report
> should just take the results of the run from the build phase.
> 2) why does it make a difference if i run mvn clean install site vs mvn
> clean; mvn install; mvn site as three separate commands
> 3) is the interaction between the various common plugins documented
> anywhere?  for example cobertura is smart enough to tell surefire to run the
> tests against the instrumented classes behind the scenes, but this is not
> documented anywhere that I have seen. what other side effects might it have?
>
>
> Kind regards,
> Dave Sag
>
>
>
>
>

Reply via email to