Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Not A Bug
-
Affects Version/s: 1.0-beta-1
-
Fix Version/s: None
-
Component/s: Standard Rules
-
Labels:None
-
Environment:HideApache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100) Java version: 1.6.0_16 Java home: C:\Java\jdk1.6.0_16\jre Default locale: en_GB, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"ShowApache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100) Java version: 1.6.0_16 Java home: C:\Java\jdk1.6.0_16\jre Default locale: en_GB, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
-
Testcase included:yes
-
Number of attachments :
Description
The RequirePluginVersions rule incorrectly ignores any versions defiend in the Super POM.
This is inconistent with the documentation,
"This rule enforces that all plugins have a version defined, either in the plugin or pluginManagement section of the pom or a parent pom."
The POM's implicit parent is the Super POM.
Expected outcome:
The attached project (to be used as an Integration Test) should pass the validate stage with Maven 2.2.1
Actual outcome:
The project build fails with:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed )
org.apache.maven.plugins:maven-clean-plugin. The version currently in use is 2.3
org.apache.maven.plugins:maven-deploy-plugin. The version currently in use is 2.4
org.apache.maven.plugins:maven-install-plugin. The version currently in use is 2.3
org.apache.maven.plugins:maven-site-plugin. The version currently in use is 2.0.1
All these plugins have their versions defined in the Super POM.
This works as designed, users should not rely on the super POM plugin versions because these change between Maven versions and render the build subject to the build environment.