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? 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
