[
http://jira.codehaus.org/browse/MSITE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl moved MNG-2193 to MSITE-442:
------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Sites & Reporting)
Fix Version/s: (was: 3.x)
Affects Version/s: (was: 2.0.3)
Key: MSITE-442 (was: MNG-2193)
Project: Maven 2.x Site Plugin (was: Maven 2 & 3)
> Add ability to exclude a report mojo from executing
> ---------------------------------------------------
>
> Key: MSITE-442
> URL: http://jira.codehaus.org/browse/MSITE-442
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Reporter: Vincent Massol
>
> Here's a use case (see also MCLOVER-19):
> * I'm working on the clover plugin
> * I have one report mojo that forks a custom lifecycle (this one instruments
> the source code, runs the tests and generate a report)
> * I'd like to have another report which simply takes an existing clover
> database and generate a report out of it
> Right now it's not possible to implement such a use case as by default all
> report mojos are executed. I'd need to exclude the first report mojo (the one
> that forks a lifecycle) from executing when the second report mojo is
> executing.
> Thanks
--
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
