I expect it to pass because the local repository has the correct version. Consider the case where you have separate GIT roots for your different modules (because they have a separate release lifecycle)
Your parent project will have version 4-SNAPSHOT The sibling child project will reference parent version 3, expecting resolution from the repository Normally you won't see much of a problem because you will be updating to the latest parent after each release... hence why this is subtle. Where I found this was when I switched the child branch to a previous stable branch to work on a bug fix... and because the wrong parent was being resolved my project would not build. Work-around has been to then switch the parent back to the matching branch. On 5 June 2015 at 11:05, Fred Cooke <[email protected]> wrote: > Your tar file is polluted with ._ stuff that ends up laying around the > place. Aside from that: > > 3.1.1 succeeds. > 3.3.3 fails > > The description of what is wrong/your expectation could be better. > > I guess I would expect it to fail, but fail because relative path POM > version doesn't match that specified. > > > On Fri, Jun 5, 2015 at 9:42 PM, 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 > > >
