The best location to ping us is on [email protected] I don't know who is always active especially on this plugin. I didn't touch it for .. years AFAIR
Arnaud On Thu, Dec 16, 2010 at 4:29 PM, Will Gwaltney <[email protected]> wrote: > Hi Pankaj, > > > > I’m no longer associated with the Cobertura plugin, and haven’t been for > some years. Hopefully somebody else on the list can help you out. > > > > Will > > > > ----------------------------------------- > Will Gwaltney > SAS Institute > [email protected] > 919-531-9025 > > "Unity trumps doctrinal purity." -- me > ----------------------------------------- > > > > From: Pankaj Tandon [mailto:[email protected]] > Sent: Thursday, December 16, 2010 10:19 AM > To: [email protected]; Will Gwaltney; [email protected]; > [email protected] > Subject: Maven Cobertura Plugin - Tests are run twice > > > > Hi guys, > > I got your email address from the plugins project info page. I had to write > to you directly as I cannot find a current forum for this plugin. > > The current version of the plugin (2.4) is causing the tests to run twice. > I saw a post here from 2006: http://jira.codehaus.org/browse/MCOBERTURA-12 > But it is dated and therefore may not be relevant. > > The solution I am suggesting will require an change in the lifecycle.xml > file: > > When a project pom is executed with the cobertura-maven-plugin pom > configured with the 'check' goal AND skipTests=false, tests run once in the > test phase via surefire and once, in the test phase as defined in > lifecycle.xml file of the plugin against the instrumented classes. > > This is a problem for long-running tests, as I would like to run the tests > only once against the instrumented code. > > If I set skipTests=true, then tests are not run by surefire AND cobertura. > That is a problem too as the tests are not run against the instrumented > classes and the check fails. > > The only way I can make the tests run ONCE is by adding skipTest=false in > lifecycle.xml AND set skipTests=true in my pom as a top level property. > > That way surefire tests are skipped and the cobertura tests run against the > instrumented code. > > Since 'check'ing the coverage must have the tests run, can I suggest adding > that <skipTests>false</skipTests> permanently in the lifecycle.xml file like > below: > > ... > <phase> > <id>test</id> > <configuration> > > <classesDirectory>${project.build.directory}/generated-classes/cobertura</classesDirectory> > <testFailureIgnore>true</testFailureIgnore> > <skipTests>false</skipTests> > <forkMode>once</forkMode> > </configuration> > </phase> > ... > > Can you please suggest if this is a viable solution? > And if so, can it be implemented? > > Thanks a lot! > > Pankaj --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
