[
http://jira.codehaus.org/browse/MCLOVER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101937
]
John Allen commented on MCLOVER-44:
-----------------------------------
This is a nasty problem isnt it and one we're suffering from too. can you maybe
change the classifier or package type or something when you're running the
clover stuff and the other plugins can key off that (ie ignore if not equal to
type jar?). this all smells of an endemic problem re customising lifecycles,
maybe you can use completely different phase names and default plugin mappings?
I expect im talking rubbish but you know what i mean:)
> Do not run quality check plugins on clovered sources as they'll generate lots
> of errors
> ---------------------------------------------------------------------------------------
>
> Key: MCLOVER-44
> URL: http://jira.codehaus.org/browse/MCLOVER-44
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Vincent Massol
> Assignee: Vincent Massol
> Priority: Critical
>
> For example, if you have checkstyle:check configured in your project, running
> clover instrumentation will lead to the clover plugin analyzing the clovered
> sources (clover modifies sources to add clover statements) thus generating
> tons of violations even though your code is correct...
> The same will happen for any *:check goal (PMD, findbugs, etc).
> Somehow we need to find a way not to run those plugins when the clover forked
> lifecycle executes...
> <private note>Mike, I think this is what you were trying to tell me and I was
> not understanding... Now I've been hit by it too... :-)</private note>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
