> -----Original Message-----
> From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
> Sent: mardi 7 novembre 2006 09:04
> To: Maven Users List
> Subject: Re: We need some explanation ...
>
> Hi Vincent,
> The architecture is quite clear now, but there remains some questions:
> - I understand that when calling clover:instrument in any phase, this
> triggers a custom lifecycle (clover LC) that runs instrumentInternal
> and then runs the tests so that clover DB gets populated. This
> lifecycle is forked so that original sources are prevented from
> ending up in artifact.
Yes, exactly.
> - the original question was about the use of process-sources: It
> seemed to me that coverage intsrumentation should be done after all
> sources are generated. Why is this not the case for clover ?
The clover:instrumentInternal goal is bound to the generate-sources phase
(the first phase for sources). The main reason is that any source generated
is usually already tested (the generators are usually tested) and there's
usually no need to write tests for it. Instrumenting the generated sources
would skew the coverage result. Now I agree that it's possible that there
are cases where you'd want the instrumentation to include generated sources.
This is not supported as of now. Actually nobody has asked for this use case
yet...
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son
interface révolutionnaire.
http://fr.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
