[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330285#comment-330285
]
Jörg Sesterhenn commented on MSITE-443:
---------------------------------------
Please reopen this issue.
With reintroduction of the "classic" reporting configuration in
maven-site-plugin 3.3 due to MSITE-684 as described here, there has been a
regression. Although I define the versions of all my report-plugins in
plugin-management maven says:
[WARNING] Some problems were encountered while building the effective model for
de.seu.maven:MyParentPOM:pom:1.2.2-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.codehaus.mojo:clirr-maven-plugin is missing. @ line 364, column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-project-info-reports-plugin is missing. @ line
368, column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 372, column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-surefire-report-plugin is missing. @ line 376,
column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.codehaus.sonar-plugins:maven-report is missing. @ line 380, column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-changes-plugin is missing. @ line 384, column 15
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-dependency-plugin is missing. @ line 414, column
15
I second the vote for a plugin-management inside of <reporting>: That way maven
could choose to resolve report-plugins only if site generation is triggered.
I am using maven 3.0.5 and maven-site-plugin 3.3.
> 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
