Hi Vincent, Vincent Massol wrote on Wednesday, April 13, 2005 11:25 AM:
> Hi, > > In preparation to implementing the clover plugin for m2, I > need to understand what are the options WRT generated > sources. Indeed clover modifies the source files (.java > files) and generate instrumented source files. > > I can see 2 options: > > 1/ Option 1: A mechanism similar to the Ant <javac> task > where there is a notion of pluggable compiler adapter. In > that case I could write a CloverCompilerAdapter. > > 2/ Option 2: Generate instrumented sources in target/ > somewhere and somehow convince the compile plugin to use > those sources rather than the ones in src/main/java. ?? I always had the impression, Clover instruments the class files only. > Please note that I'd like to support the use case where main > sources are instrumented and they generate clover data either > when the unit tests are run or when functional tests are run > or when a user manually brings up the application to test it. > > Also, I'd prefer that instrumented sources do not > inadvertently find their way in the release and thus I'd like > to keep the 2 main source trees separate (unmodified files > and modified ones) so that running: > > m2 clover:on test:test clover:report What bugs me most is that running test:report will run the tests again! I am not sure about any mechanism in M2 preventing this. [snip] - J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
