[#CLOV-150] maven-clover-plugin should provide "skip" option

Clover

maven-clover-plugin should provide "skip" option

Created: 22/Jan/08 10:33 AM Updated: 28/May/08 11:51 PM

Component/s:

Maven plugin

Affects Version/s:

None

Fix Version/s:

2.3.1

Time Tracking:

Not Specified

Environment:

Linux, jdk1.5, maven 2.0.7 and 2.0.8, maven-clover-plugin 3.6

Participants:	Erez Nahir, John Allen and Nick Pellow [Atlassian]
Since last comment:	26 weeks, 4 days ago
Resolution Date:	28/May/08 11:51 PM
Labels:

Description

« Hide

In a multi module maven project, some modules are not standard java projects (cpp for example), we need a way to let the component to force maven-clover-plugin to be skipped.
This is similar to the skip option provided by surefire plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
This is a blocking issue for our team to use clover in our project.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

John Allen added a comment - 21/Feb/08 01:31 PM

I agree <skip>true</skip> would be good, it seems to be another one of those undocumented maven standards but as a workaround, IIRC, you can simply redeclare the plugin execution but assign the phase to be null, e.g. <phase></phase>, this will prevent the plugin from running in that project

[ Permlink | « Hide ]

Nick Pellow [Atlassian] added a comment - 28/May/08 11:51 PM

Hi,

This has been implemented for the very recent release of the maven-clover2-plugin.
This issue was a duplicate of http://developer.atlassian.com/jira/browse/CLMVN-33.

Please note however that there has been an artifactId change in this version of the plugin.
maven-clover-plugin --> maven-clover2-plugin
clover:instrument --> clover2:instrument etc...