[
http://jira.codehaus.org/browse/MSITE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MNG-3949 to MSITE-454:
-----------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Plugins and Lifecycle)
Fix Version/s: (was: 2.x)
3.0-alpha-1
Affects Version/s: (was: 2.1.0-M1)
(was: 2.0.9)
Key: MSITE-454 (was: MNG-3949)
Project: Maven 2.x Site Plugin (was: Maven 2 & 3)
> Don't use aggregator mojos for default report set
> -------------------------------------------------
>
> Key: MSITE-454
> URL: http://jira.codehaus.org/browse/MSITE-454
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-1
>
>
> For a POM snippet
> {code:xml}
> <reporting>
> <plugins>
> <plugin>
> <artifactId>maven-javadoc-plugin</artifactId>
> </plugin>
> </plugins>
> </reporting>
> {code}
> all available mojos of the plugin will be used as reports. This includes
> mojos marked with {...@aggregator}} although binding aggregators into the
> lifecycle can be troublesome, especially if they additionally fork the
> lifecycle.
> Hence I suggest we exclude aggregators from report sets unless explicitly
> configured by the user.
--
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
