Re: Cobertura Maven Plug-in Status

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.