Yes, I have seen the files in the mojo-sandbox.
I started with them, but after a dozen or so refactorings and best practices in mojo development, they no longer resemble the original donation.
I credit the original donator (Will Gwaltney) in the pom and the code.
I have plenty of experience with Cobertura and have made greate strides in bringing this mojo up to speed with both Cobertura and the Maven Mojo framework.
The design I settled on avoids some of the pitfalls with large projects that the original design contained.
My patch against jcoverage, to handle large projects, inspired the fork of jcoverage that is now called Cobertura.
The clover plugin is a good example, but it appears that Clover instruments the source code before the compile, unlike cobertura, which instruments the compiled classes (via the ASM library).
Based on my limited ability to run the clover plugin, it appears that the clover plugin also suffers from the instrumented classes in the package syndrome that I am facing with the cobertura plugin.
I am attempting to obtain a clover license to verify this.
The jcoverage plugin (which should have been a good example) doesn't even compile anymore, due to a missing AbstractPlugin class. shrug