franz see <[EMAIL PROTECTED]> writes: > Anyway, I'm not sure though if another goal would be bound to the same phase > as instrumentInternal. Though I haven't really disected the code to its very > core, the architecture provided in [1] seems to indicate that it is forked > to its own lifecycle (clover lifecycle). But I haven't trace that part yet > where forking happens so I'm not sure if that architectural design is still > updated. >
Yes, there is a custom lifecycle, see [1]. But I do not know what really happens with this lifecycle fork: I must confess I am still confused by this forking stuff. According to the descriptor, the clover plugin runs: generate-sources, test and integration-test phases, with goal instrumentInternal bound to generate-sources. This implies that no other goals from other plugins are run in this phase, so generated sources (eg. from modello plugin) are not covered by clover's instrumentation . If someone with more knowledge than me is lurking around, help appreciated. regards,, [1] http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
