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

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

Thanks for the hint. Commented on MNG-5477.
                
> add a reportingManagement section
> ---------------------------------
>
>                 Key: MSITE-443
>                 URL: https://jira.codehaus.org/browse/MSITE-443
>             Project: Maven Site Plugin
>          Issue Type: Bug
>         Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>            Reporter: Indrajit Raychaudhuri
>             Fix For: 3.0
>
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to