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/03/23 06:32:13 UTC

[jira] Updated: (MNG-3949) Don't use aggregator mojos for default report set

     [ http://jira.codehaus.org/browse/MNG-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3949:
------------------------------

    Fix Version/s: 2.x

> Don't use aggregator mojos for default report set
> -------------------------------------------------
>
>                 Key: MNG-3949
>                 URL: http://jira.codehaus.org/browse/MNG-3949
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0.9, 2.1.0-M1
>            Reporter: Benjamin Bentmann
>             Fix For: 2.x
>
>
> 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