Please correct me if I'm misunderstanding something (since it's been months since I looked at clover) but isn't the heart of the problem that you add the clover source to the project sources? I don't think you should do this. It's not technically part of the project source and source reports should not scan it.
-----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006 2:51 PM To: 'Maven Developers List' Subject: General issue with clover plugin requiring creative thinking... Hi, I have found an important issue with the clover plugin use case. Clover instrument sources. The clover plugin redirect maven sources to point to the clovered sources. This is all fine for most plugins as they'll now operate on the modified sources (compile, jar, install, deploy, etc). However there's a set of plugins for which it is NOT right: the quality plugins that check the sources for best practices (checkstyle, pmd, findbugs, etc). They are checking the clovered sources and of course they're finding lots of violations (as the code added by clover is not following the project practices)... Has anyone any idea how I could get around this in the clover plugin? Thanks a lot -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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
