[jira] Commented: (MNG-1931) add a reportingManagement section

["John Allen (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-1931?page=comments#action_58533 ] 

John Allen commented on MNG-1931:
---------------------------------

Any thoughts re moving this up the priority ladder? After all one of the key benefits of using maven is the reduction in duplicated configs and currently I am not able to share any of my reporting settings across projects.

Additionally re reporting plugin configs affecting build plugin settings. 

I uses a number of plugins for both reporting and compliance/governance checks, currently javadoc warnings, pmd, checkstyle and test coverage. I would like to be able to run reporting against one set of configs and have build uses others. Ie. reporting tends to use quite a harsh set of rules for PMD/Checkstyle whereas my compliance build (which fails the build if a governance setting is not met) uses a more relxed config. How can i achieve this separation on configs for plugins that are used in both reporting and build?



> add a reportingManagement section
> ---------------------------------
>
>          Key: MNG-1931
>          URL: http://jira.codehaus.org/browse/MNG-1931
>      Project: Maven 2
>         Type: Bug

>   Components: POM, Design, Patterns & Best Practices
>  Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>     Reporter: Indrajit Raychaudhuri
>      Fix For: 2.1

>
>
> Consider the following POM:
> {code:xml}
> <!-- ... ... -->
> <!-- ... ... -->
> <build>
>     <pluginManagement>
>         <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-javadoc-plugin</artifactId>
>             <configuration>
>             <author>false</author>
>             </configuration>
>         </plugin>
>     </pluginManagement>
> </build>
> <!-- ... ... -->
> <!-- ... ... -->
> <reporting>
>     <plugins>
>         <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-javadoc-plugin</artifactId>
>         </plugin>
>     </plugins>
> </reporting>
> <!-- ... ... -->
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the {{<pluginManagement/>}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{<reporting/>}} section doesn't use the {{<pluginManagement/>}} section at all.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org