Brett Porter <[EMAIL PROTECTED]> wrote on 31-01-2006 18:46:42: > On 2/1/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Okay I have changed my build so that the checkstyle etc all happen on the > > verify phase, and have updated to use the latest snapshot version of > > cobertura plugin. > > > > [mvn install] works fine - all is as expected. > > > > but [mvn site] continues to break as follows: > > > Do you have zero-length classes, or is this something else? I recall seeing > AIOOBE as a bug back in jcoverage some time back, but I'm not sure this is > the same. >
yes that's exactly what is happening. the second (redundent) instrumentation generates 0 length classes. I am not sure what AIOOBE means. > I stress that this all used to work fine with maven 2.0 and the old > > cobertura plugin. I suspected a bug in the surefire reporting rather than > > in cobertura, and so removed any references to surefire from my reporting > > but i get pretty much the exact same result. > > > The cobertura plugin was changed around mid-Dec to better use the facilities > provided by Maven 2.0.1 for defining the lifecycle. > shame it broke eh. > Does anyone out there have a working example of maven 2.0.2 using cobertura > > to instrument classes and generate a report? If so please would you care to > > share your wisdom? Or would you recommend rolling back to maven 2.0 until > > these issues are fixed? > > > > We use it for: > https://svn.apache.org/repos/asf/maven/repository-manager/trunk > I see no reference at all to cobertura in https://svn.apache.org/repos/asf/maven/repository-manager/trunk/pom.xml dave
