[
http://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204400#action_204400
]
Dennis Lundberg commented on MSITE-443:
---------------------------------------
Jason,
If this the issue of moving all reporting plugins configuration into the Site
Plugin? Is this a requirement for Maven 3? Would it be possible to make this
work for Maven 2.1+ as well?
> add a reportingManagement section
> ---------------------------------
>
> Key: MSITE-443
> URL: http://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
> Reporter: Indrajit Raychaudhuri
> Fix For: 3.0-alpha-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
