You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/01/02 11:50:19 UTC

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

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.1.0-M1, 2.0.9
            Reporter: Benjamin Bentmann


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

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.

     [ 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

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.

     [ 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

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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.

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

Olivier Lamy updated MSITE-454:
-------------------------------

    Fix Version/s:     (was: 3.0-alpha-1)

> 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
>
> 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

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.

    [ 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