[MPIR-300] Reporting plugins are reported with wrong version if version specified via pluginManagement

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.8.1
• Component/s: plugin-management

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"

• Assignee: Herve Boutemy
• Reporter: Thomas Reitmayr
• Created: 09/Sep/14 06:58
• Updated: 11/Sep/15 04:26
• Resolved: 23/Aug/15 21:07

Description

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 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 (and this version is actually used for generating the surefire report) but the plugins.html report says 2.17 (the latest version).

Issue Links

• is depended upon by: MPOM-73 upgrade MPIR to get MPIR-300 fix
• relates to: MSITE-443 add a reportingManagement section