[ 
https://jira.codehaus.org/browse/MSITE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330286#comment-330286
 ] 

Jörg Sesterhenn commented on MSITE-516:
---------------------------------------

reportPlugins is going to be removed in favor of [classic reporting 
configuration|http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Classic_configuration_Maven_2__3]
 (which still hat 
[issues|http://jira.codehaus.org/browse/MSITE-443?focusedCommentId=330285&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-330285]).
 This issue stays nonetheless.
                
> reportPlugins should/could inherit more information from pluginManagement
> -------------------------------------------------------------------------
>
>                 Key: MSITE-516
>                 URL: https://jira.codehaus.org/browse/MSITE-516
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>          Components: inheritance
>    Affects Versions: 3.0-beta-2
>         Environment: Apache Maven 3.0 (r1004208; 2010-10-04 15:50:56+0400)
> Java version: 1.6.0_22
>            Reporter: Oleg Estekhin
>
> At the moment the plugins configured in the reportPlugins section inherit 
> only the version specified in the pluginManagement section as described in 
> https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html#Maven3.xandsiteplugin-VersionResolution
>  .
> Additional configuration (for example, configuration for 
> maven-javadoc-plugin) is effectively should be entered twice - once in either 
> build/pluginManagement/plugins or build/plugins to be used by the usual build 
> process, and once in the 
> build/plugins/maven-site-plugin/configuration/reportPlugins to be used by the 
> site generation.
> Please, consider possibility for reportPlugins to inherit the same amount of 
> configuration from the pluginManagement as is being inherited by usual build 
> plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to