> -----Original Message----- > From: Jörg Schaible [mailto:[EMAIL PROTECTED] > Sent: mercredi 13 avril 2005 11:44 > To: Maven Developers List > Subject: RE: [M2] Clover plugin ideas and questions
[snip] > ?? I always had the impression, Clover instruments the class files only. See http://cenqua.com/clover/doc/cli/cloverinstr.html The reason you had this impression is probably because the clover:setup task registers a CompilerAdapter to the Ant's javac task. > > > 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. I agree. It'll simply act on an existing clover database. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
