You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2014/05/11 16:43:10 UTC

[jira] (MSITE-454) Don't use aggregator mojos for default report set

     [ https://jira.codehaus.org/browse/MSITE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy closed MSITE-454.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.4
         Assignee: Herve Boutemy

fixed with MSHARED-266: see this issue for details on the solution, which is not by directly removing aggregator mojos

> Don't use aggregator mojos for default report set
> -------------------------------------------------
>
>                 Key: MSITE-454
>                 URL: https://jira.codehaus.org/browse/MSITE-454
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>            Reporter: Benjamin Bentmann
>            Assignee: Herve Boutemy
>             Fix For: 3.4
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)