Re: [all] replacing cobertura with jacoco in parent pom

2013-03-30 Thread Honton, Charles
I have been experimenting with jacoco in the ClassScan sandbox. I am impressed with how easy jacoco is to setup and run. Although published benchmarks show jacoco and cobertura having roughly equivalent performance impact, the maven-cobertura-plugin has a twist that makes cobertura much slower:

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread sebb
On 25 March 2013 17:48, Phil Steitz wrote: > On 3/25/13 9:08 AM, Gary Gregory wrote: >> Replacing one test coverage plugin in the parent POM with another is >> probably OK, but must be tested. >> >> But if someone decides to remove this test coverage plugin from the parent >> POM, then make sure t

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Phil Steitz
On 3/25/13 9:08 AM, Gary Gregory wrote: > Replacing one test coverage plugin in the parent POM with another is > probably OK, but must be tested. > > But if someone decides to remove this test coverage plugin from the parent > POM, then make sure to enable it is all the other components. Why? The

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Gary Gregory
Replacing one test coverage plugin in the parent POM with another is probably OK, but must be tested. But if someone decides to remove this test coverage plugin from the parent POM, then make sure to enable it is all the other components. Gary On Mon, Mar 25, 2013 at 11:34 AM, Phil Steitz wrot

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Phil Steitz
On 3/25/13 8:12 AM, Emmanuel Bourg wrote: > Is it possible to disable cobertura at the component level only? The short answer is no. Its bugged-ness extends to ignoring the disabling config. Phil > > > Emmanuel Bourg > > > Le 25/03/2013 11:01, Luc Maisonobe a écrit : >> Hi all, >> >> We have alr

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Emmanuel Bourg
Is it possible to disable cobertura at the component level only? Emmanuel Bourg Le 25/03/2013 11:01, Luc Maisonobe a écrit : > Hi all, > > We have already discussed about some problems with the cobertura maven > plugin (see and >

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Phil Steitz
On 3/25/13 3:21 AM, Adrian Crum wrote: > Is there any way a project can select its own code coverage tool? > I don't like the top-down, all-or-nothing approach to Commons > build files. Big +1 to this. Lets just please drop this from the parent pom. Phil > > -Adrian > > On 3/25/2013 10:01 AM, L

Re: [all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Adrian Crum
Is there any way a project can select its own code coverage tool? I don't like the top-down, all-or-nothing approach to Commons build files. -Adrian On 3/25/2013 10:01 AM, Luc Maisonobe wrote: Hi all, We have already discussed about some problems with the cobertura maven plugin (see

[all] replacing cobertura with jacoco in parent pom

2013-03-25 Thread Luc Maisonobe
Hi all, We have already discussed about some problems with the cobertura maven plugin (see and ). As a summary, cobertura seems to not be maintained, there are some bugs that trigger errors with [math] (see