Hello all, I have a fairly large build in which we use cobertura extensively to look at unit test code coverage for our project. We also have separate integration tests that we would like to run using these instrumented binaries. There is some good documentation on how to accomplish that here:
http://mojo.codehaus.org/cobertura-maven-plugin/instrumentingDeploymentArtifact.html While that would work for a simple case, I'm struggling with trying to visualize how this would work in a complex case. We have several separate builds that accumulate to make up the install package that we then push to our integration testing systems. So everyone one of our couple hundred jar's which are fed from all these builds would need to be published to a Maven repository so that the install builds could pick them up. But if I push them to my standard SNAPSHOT repository it would overwrite my existing non-instrumented versions. We only envision needing this run on a nightly basis. One suggestion that has been proposed is to do the "publish with classifier" thing and a profile that turns on cobertura. https://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html Frankly, I'm not sure how that plumbing would work at this point, but I suppose it's possible. Having said that, I think we just got done having that conversation on this list and the answer is that that is "not the maven way". I'm positive I'm not the first one in this boat. Any thoughts? -Jim --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
