Le 2013-04-05 00:10, Gary Gregory a écrit :
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?
Yes !
I already use Jacoco elsewhere and am very happy with it. It is also
used in our
Sonar instance if I remember correctly.
The only point I had to adjust in the other project was to set up
manually an entry in
the site menu to point to the generated html pages, as jacoco was not
fully integrated
in the regular reports produced by maven. Is there a complete
integration available now?
Luc
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
