Thomas Reitmayr created MPIR-300:
------------------------------------
Summary: Reporting plugins are reported with wrong version if
version spedified via pluginManagement
Key: MPIR-300
URL: https://jira.codehaus.org/browse/MPIR-300
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: plugin-management
Affects Versions: 2.7
Environment: Apache Maven 3.2.1
(ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00)
Maven home: <...>/maven-3.2.1
Java version: 1.7.0_07, vendor: Oracle Corporation
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-34-generic", arch: "amd64", family: "unix"
Reporter: Thomas Reitmayr
Attachments: mvn.log, plugins.html, pom.xml
My pom.xml specifies all plugin versions including the ones for plugins used in
the reporting section via pluginManagement. Accoring to
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution
and the ticket https://jira.codehaus.org/browse/MSITE-443 this is fully
supported by the maven-site-plugin.
Unfortunately the maven-project-info-report-plugin does not seem to adhere this
version resolution which results in a wrong version in the report.
The attached example gives a pom.xml, the log file when generating the site,
and the resulting plugins.html. The version to look at is from the
maven-surefire-report-plugin, which has 2.16 specified in the pluginManagement
section, which the plugins report says 2.17 (the latest version).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
