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/06/09 22:06:11 UTC

[jira] (MSITE-523) Configuring build and reporting goals (under reportPlugins) requires duplication

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

Herve Boutemy commented on MSITE-523:
-------------------------------------

MSITE-516 is now fixed: configuration from pluginManagement will be injected into reports

do you expect something more, since you call this a workaround?

> Configuring build and reporting goals (under reportPlugins) requires duplication
> --------------------------------------------------------------------------------
>
>                 Key: MSITE-523
>                 URL: https://jira.codehaus.org/browse/MSITE-523
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>          Components: inheritance
>    Affects Versions: 3.0-beta-3
>         Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_22
>            Reporter: Andreas Sewe
>
> Many plugins ({{maven-checkstyle-plugin}}, {{maven-javadoc-plugin}}, {{maven-pmd-plugin}}) have both build and reporting goals. Unfortunately, the plugin configuration done in the build section of the POM does not carry over to the plugin configuration done for the {{reportPlugins}} of the {{maven-site-plugin}}. Consequently, one has to duplicate any custom configuration which should apply to both build and reporting, e.g., the {{configLocation}} configuration element of the {{m-checkstyle-p}}. :-(
> Note that a workaround is possible, once MSITE-516 is resolved; still, I consider this to be an independent issue.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)