Maybe nevermind, I checked out the source and tests for the clover plugin and there is a test to instrument the tests and it verifies the plugin works as expected (line count increases with property set to true).
I will double-check my project setup to determine what is wrong. Jeff jblack wrote: > > Lukas, > > Thanks for the ideas, I think this is the right track. > > However, setting maven.clover.instrument.tests=true did not produce and > change to the clover report (source lines of code, or otherwise). > Tracking the plugin.jelly, the path to the test source is being included > as a fileset to clover-setup, but from there I'm not sure what I might be > doing wrong...? > > > Jeff > > > Lukas Theussl-3 wrote: >> >> Can't you get that using the maven.clover.instrument.tests and/or >> maven.clover.includes/excludes properties? >> >> -Lukas >> >> jblack wrote: >>> Clover will show me source lines of code, is there a technique to get >>> only >>> Test source lines of code. >>> >>> Example like: Code LOC: 451 Test LOC: 586 Code to Test Ratio: 1:1.3 >>> >>> Or is there an integrated maven report that will do this for me? >>> >>> >>> Jeff >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- View this message in context: http://www.nabble.com/-m1--Report-showing-code-to-test-ratio--tf4142921s177.html#a11816493 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
