RequirePluginVersions breaks when using project.parent.groupId and
project.parent.version.
------------------------------------------------------------------------------------------
Key: MENFORCER-30
URL: http://jira.codehaus.org/browse/MENFORCER-30
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Reporter: Nick Stolwijk
Assignee: Brian Fox
Priority: Trivial
We were using a obsolete but working child pom file, like:
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.example.petstore</groupId>
<artifactId>petstore</artifactId>
<version>0.2-SNAPSHOT</version>
</parent>
<groupId>${project.parent.groupId}</groupId>
<artifactId>petstore-common</artifactId>
<version>0.2-SNAPSHOT</version>
<packaging>jar</packaging>
<name>Common module</name>
<description>The Common module.</description>
</project>
The rule will fail, when the child is not in the local or a remote repository,
because ${project.parent.groupId} and org.example.petstore are not the same and
the artifact can not be found.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
