On Thu, Apr 4, 2013 at 4:03 PM, sebb <seb...@gmail.com> 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. >
OK, but which one? I know some projects use Clover but I'd rather we use another FOSS tool. I know Jacoco has been mentioned.. maybe [math] wants to be the guinea pig? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
