You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Stephen Godwin (JIRA)" <ji...@apache.org> on 2010/11/16 16:40:13 UTC
[jira] Created: (ARIES-494) Missing relativePath element in parent
section of pom.xml files cause a build from scatch to fail with Maven 3
Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3
---------------------------------------------------------------------------------------------------------------
Key: ARIES-494
URL: https://issues.apache.org/jira/browse/ARIES-494
Project: Aries
Issue Type: Bug
Affects Versions: 0.3
Reporter: Stephen Godwin
Fix For: 0.3
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (ARIES-494) Missing relativePath element in
parent section of pom.xml files cause a build from scatch to fail with
Maven 3
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-494 started by Jeremy Hughes.
> Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-494
> URL: https://issues.apache.org/jira/browse/ARIES-494
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Stephen Godwin
> Assignee: Jeremy Hughes
> Fix For: 0.3
>
> Attachments: parentRelativePath.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-494) Missing relativePath element in parent
section of pom.xml files cause a build from scatch to fail with Maven 3
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes reassigned ARIES-494:
-----------------------------------
Assignee: Jeremy Hughes
> Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-494
> URL: https://issues.apache.org/jira/browse/ARIES-494
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Stephen Godwin
> Assignee: Jeremy Hughes
> Fix For: 0.3
>
> Attachments: parentRelativePath.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-494) Missing relativePath element in parent
section of pom.xml files cause a build from scatch to fail with Maven 3
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes resolved ARIES-494.
---------------------------------
Resolution: Fixed
> Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-494
> URL: https://issues.apache.org/jira/browse/ARIES-494
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Stephen Godwin
> Assignee: Jeremy Hughes
> Fix For: 0.3
>
> Attachments: parentRelativePath.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-494) Missing relativePath element in parent
section of pom.xml files cause a build from scatch to fail with Maven 3
Posted by "Stephen Godwin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Godwin updated ARIES-494:
---------------------------------
Attachment: parentRelativePath.patch
Patch to add relativePath elements to Parent section of pom.xml files.
> Missing relativePath element in parent section of pom.xml files cause a build from scatch to fail with Maven 3
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-494
> URL: https://issues.apache.org/jira/browse/ARIES-494
> Project: Aries
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Stephen Godwin
> Fix For: 0.3
>
> Attachments: parentRelativePath.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.