I understand your point, but the explaination you provide is based on how it is implemented...and not on how it is specified.
The fact that maven can resolve the same artifact when it is a dependency means that it is not a limitation but an implementation issue. That looks bad to me to have to add a fake repository to have Maven resolve the parent SNAPSHOT. Note that in my example the foo repository does not exist at all neither http://foo URL. It is juste a fake declaration in the settings.xml. This means that maven at the end, failover and still uses the mirror to go to Nexus and retrieve the SNAPSHOT parent. Why (repo!=mirror) applies to Parent and not to project dependencies ? At the end we added the fake repo declaration to all our settings.xml, but that's not very elegant, but it works. -- View this message in context: http://maven.40175.n5.nabble.com/Parent-SNAPSHOT-not-resolved-Maven-2-2-1-3-0-4-Nexus-repo-tp5772374p5772379.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
