You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anthony Whitford (JIRA)" <ji...@codehaus.org> on 2011/07/31 14:58:43 UTC
[jira] Commented: (MSITE-443) add a reportingManagement section
[ https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274696#comment-274696 ]
Anthony Whitford commented on MSITE-443:
----------------------------------------
I like Sven's idea. Ultimately, I am looking for a way to say, "Use javadoc 2.8" _once_ -- this should affect both the <build> and <reporting> sections, otherwise my pom violates the DRY principle.
> add a reportingManagement section
> ---------------------------------
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
> Reporter: Indrajit Raychaudhuri
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira