On Fri, Apr 5, 2013 at 4:30 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
> On 4/4/13 1: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. > +1 > > > > However, I think it is important that some code coverage tool is used. > > I would say let components decide whether they want to a) include > something b) use Sonar c) nothing. > All components 'should' provide coverage reports IMO, so configure one in parent. If you really do not want one, then you have to 'configure by exception' and remove it. I think we are to the point now where we want to say goodbye to Cobertura and hello to Jacoco. Gary > > Phil > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- 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
