There is a point about classpath ordering (caused by some hashMap/linkedHashMap stuff) which is fixed in the current snapshot for exampleThat is to say : cobertura, when executing instrumented tests, is not using the same classpath as the one defined in maven (it could be problematic !...)
I think lots of other stuff have been fixed since the 2.2 release (which release date is dec 2007 !) Maybe current dev version is not enough stable to release ... but when I look at revision logs over SVN, I see the two last commits are dated from 21/12/2008 and 21/07/2008 :-( It is too bad to use SNAPSHOT build in order to have this fixed. Cheers, Frederic 2009/4/29 Stephen Connolly <[email protected]> > My understanding is that there is an issue with aggregating coverage > results for a multi-module project and forking the build... > > Clover faces the same issue but is farther down the road, and it looks like > there is no good solution for Maven 2.x (i.e. need the build plan stuff from > 3.x) > > The Cobertura plugin seems to work fine otherwise, why would it need a new > release? > > -Stephen > > 2009/4/29 Stevo Slavić <[email protected]> > > Hello Codehaus Mojo Users, >> >> Are there any active Cobertura Maven Plug-in developers? Project appears >> to be dead... >> >> Regards, >> Stevo. >> > > -- Frédéric Camblor
