« Return to Thread: Cobertura Maven Plug-in Status

Re: Cobertura Maven Plug-in Status

by Stevo Slavic :: Rate this Message:

One more IMO interesting new mojo would be "cobertura:save-coverage-data" which would help overcome obstacle Cobertura has (see last Q in Cobertura FAQ), when e.g. tests run in integration-test phase are actually functional (selenium) tests running against web application deployed in some embedded server started within maven build by a maven plugin, like Jetty. Currently Jetty server stops but as it runs in same JVM as Maven build, and because Cobertura writes coverage data only on JVM exit via shutdown hook, these data get written too late to be included in cobertura report. I would create jira issue, maybe even contribute implementation, but if there's no active developers to have a look at it and make a release all the effort would be in vain.

Regards,
Stevo.

2009/4/29 Stevo Slavić <sslavic@...>

I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.

About aggregating coverage results in a multimodule project, isn't it enough to
resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;

have users configure cobertura:instrument mojo at parent and thus inherited by every child;
implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?

Regards,
Stevo.

2009/4/29 Stephen Connolly <stephen.alan.connolly@...>

My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...

Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)

The Cobertura plugin seems to work fine otherwise, why would it need a new release?

-Stephen

2009/4/29 Stevo Slavić <sslavic@...>

Hello Codehaus Mojo Users,

Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...

Regards,
Stevo.

« Return to Thread: Cobertura Maven Plug-in Status