Maven 3.0.3 fails to use relativePath for parent pom location.
--------------------------------------------------------------
Key: MNG-5086
URL: http://jira.codehaus.org/browse/MNG-5086
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0.3
Environment: Windows 7
Reporter: Ryan J
Attachments: maven-dependency-grouping.zip
After updating to Maven 3.0.3 I've noticed it fails to use the 'relativePath'
I've specified in the 'parent' section of my POMs. The
[documentation|http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_parent]
states:
{quote}
Maven looks for the parent POM first in this location on the filesystem, then
the local repository, and lastly in the remote repo.
{quote}
However, this does not appear to be the case. I'll attach an example project
(please excuse the inaccurate name). To reproduce:
1) Go to the *group* module and run {{mvn clean install}}
2) Go to the *moduleA* module and run {{mvn compile}}
Step one should install the modules *depends*, *moduleB* and *group* to the
local repository. The *maven-dependency-grouping* module will _not_ be
installed to the local repository. At step two, *moduleA* should compile, but
fails with the (partial) error:
{quote}
Could not find artifact
maven-dependency-grouping:maven-dependency-grouping:pom:0.1-SNAPSHOT in...
{quote}
According to the documentation, the above dependency should get resolved via
the 'relativePath' specified in the 'parent' element of the POM. Maven 2.2.1
behaves correctly when repeating the above steps.
--
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
