[ARIES-494] Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3
• Fix Version/s: 0.3
• Assignee: Jeremy Hughes
• Reporter: Stephen Godwin
• Created: 16/Nov/10 15:39
• Updated: 08/Jan/11 12:37
• Resolved: 29/Nov/10 15:49

Description

If you are building Apache Aries from scratch with Maven 3 using the instructions from http://incubator.apache.org/aries/buildingaries.html
it fails at the 'mvn clean' step with several errors like:

[ERROR] The project org.apache.aries:eba-maven-plugin:0.3-incubating-SNAPSHOT (/home/godwins/aries/aries/eba-maven-plugin/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.apache.aries:java5-parent:pom:0.3-incubating-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 25, column 13 -> [Help 2]

Even with the Aries parent project already installed in the Maven repository several warnings about the parent ID not matching the path appear.
Reading the compatibility notes for Maven 3 (https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html) it appears we need a relativePath element in the parent section of the pom.xml files.

I have a patch that fixes this problem which I will attach to this defect.
I have tested that with the patch applied to revision 1035298 Aries continues to build with Maven 2 and also now builds with Maven 3.