commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Crum <>
Subject Re: [ALL] Cobertura and Parent POM
Date Thu, 04 Apr 2013 20:53:17 GMT
Thank you for working on this.

The original proposal was to replace Cobertura with something else. I 
asked that the sub projects have an option to use whatever reporting 
tool they want. So, it would be fine if some other reporting tool was 
the default as long as sub projects can use something else.


On 4/4/2013 9:03 PM, sebb wrote:
> CP 28 moved Cobertura to a profile called "reporting".
> The profile was activated by default, but could be disabled by using
> -DskipReports=true
> or
> -P!reporting
> IIRC, the idea was to move expensive (long-running) reports to a profile
> that could be disabled if necessary.
> However Cobertura causes problems with some projects, and the project seems
> to be unmaintained, so perhaps it would be sensible to disable Cobertura by
> default.
> In which case the profile and property should be renamed to reflect the
> fact that it only affects Cobertura.
> Possibly even drop Cobertura entirely from the parent POM.
> However, I think it is important that some code coverage tool is used.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message