You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/12/31 07:20:55 UTC
[jira] Commented: (MSITE-454) Don't use aggregator mojos for
default report set
[ http://jira.codehaus.org/browse/MSITE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204670#action_204670 ]
Brett Porter commented on MSITE-454:
------------------------------------
something the new site plugin will need to sort out
> 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