Hi,
I've just realized that there's work to be done on the clover plugin if we
want it to support aggregated clover reports. By aggregated reports, I mean
getting a single report for all modules. Right now this is possible but each
module will only contribute coverage for its own code. I'd like that
coverage generated by a module on some other module's code also gets
counted.
For this I'm planning to try implementing the following:
* Modify clover:instrument so that the forked lifecycle extends till the
install phase
* Create an internal clover mojo bound to the install phase that will
created a clovered version of the project's artifact as an attached artifact
(classifier = "clover").
* Handle the different type of packaging. For example for a WAR packaging,
add the clover jar to the attached clovered WAR, etc.
* Modify the clover:instrumentInternal so that for any dependency artifact,
it looks for the clovered version in the repo and adds it instead of the
non-clovered version.
As this is pretty involved I'd like to be sure this is the right thing to
do.
Thanks for any feedback!
-Vincdent
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
