Hi, I have started integrating Clover into Maven. I have actually something working as demonstrated on http://raccoon.sourceforge.net/new/ (click on "Maven reports" and then on "Test Coverage").
I want to know if it is ok to commit that in our CVS ? I have had to modify the build files for core, doc, and test. It is completely transparent (by default a property named maven.compile.clover is set to false, i.e. no test coverage) What remains to do : - ATM you need to put clover.jar in your anthome/lib and as a dependency in your project. I would like it to be completely transparent for the project. I'm eager to commit but I wanted to check with you first ... :-) Note: The only "issue" that I can see is that clover is free for all non-commercial projects only (however, Cortex, the company creating Clover seem ok for us to redistribute the clover jar). It is a plugin I'd like to see integrated in Maven as it is the best test coverage tool that I have seen and by far. The problem is that I don't know how I could write such a plugin with no impact on existing ones (core, test, doc). The same issue will happen with Jalopy/JRefactory (but it is easier for them as they don't need to modify the compile target, etc). Thanks -Vincent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
