[
https://jira.codehaus.org/browse/MNG-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325183#comment-325183
]
Petr Bodnar commented on MNG-5477:
----------------------------------
Hopefully this gets fixed as soon as possible because now you get quite a lot
of warnings (depending on how many reporting plugins you use) which in fact
shouldn't be there because they are *misleading*. As stated in the description:
"The plugin version actually used seems to be the one specified in the
pluginManagement section of the parent POM."
Yes, there is a workaround, repeating the plugin version in the <reporting>
section, but getting rid of this DRY principle violation is exactly one of the
main reasons why many users made the switch to Maven 3. So maybe reconsider the
bug priority?
> "malformed POM" warning issued when no version in reporting section
> -------------------------------------------------------------------
>
> Key: MNG-5477
> URL: https://jira.codehaus.org/browse/MNG-5477
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 3.0.5
> Environment: Ubuntu 12.04 / Oracle JDK 7u17 / Maven 3.0.5 / m-site-p
> 3.2
> Reporter: Wolf Geldmacher
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: mvn-site.zip
>
>
> When "mvn site" is run on the project attached Maven twice complains that
> "'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-project-info-reports-plugin is missing", while
> the documentation on
> http://maven.apache.org/plugins/maven-site-plugin/maven-3.html clearly states
> that "When used with Maven 3, a report plugin version can be empty (like
> build plugins)."
> The plugin version actually used seems to be the one specified in the
> pluginManagement section of the parent POM, though.
--
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
