On 5 June 2015 at 10:58, Tamas Cservenak <[email protected]> wrote:
> Same here, testcase does same as for you: > https://gist.github.com/cstamas/dd6a000e97b2c5333f01 > > But isn’t this the intended way? > If parent found on relative path, it takes precendence over one coming > from local/remote repo? > only if the GAV matches If the project omits the project.parent.version then we should take whatever version is at that path, but if we specify a different GAV then maven should resolve from the repo... currently 3.3.1&3.3.3 resolve from the repo if the GA differs. 3.2.5 also resolved from the repo when the versions differ. In any case I believe I have fixed this with https://github.com/apache/maven/commit/40d5087b6b134842e2b61a567dbb4bfbcfab7ae6 > > As per http://maven.apache.org/pom.html#Inheritance > > "Notice the relativePath element. It is not required, but may be used as a > signifier to Maven to first search the path given for this project's > parent, before searching the local and then remote repositories." > > -- > Thanks, > ~t~ > > On 5 Jun 2015 at 11:42:42, Stephen Connolly ( > [email protected]) wrote: > > https://issues.apache.org/jira/browse/MNG-5840 > > Can some other people see if this test case I attached to this issue is > replicated in their environments? > > I've been badly bitten by this a couple of times (and worse for me, I have > a project that needs 3.3.1+ to build due to bugs that were only fixed in > the 3.3 series) > > I only now had the time to try and create a minimal test case > > -Stephen >
