Thanks for the clear explanation. All our artifacts are served by our Nexus Repository Manager (external and internal). All our repositories (hosted and proxy) are managed by Nexus, this is why our settings.xml and parent poms does not need to refer to other repositories because we want to control all from Nexus.
So declaring a fake snapshot repository will help Maven re-route resolution to a parent pom... BTW if you replace the snapshot parent by a release version, the same problem appear despite the maven central in super pom... Again adding the fake repository helps solving the case. I am still not convinced it is a feature ;-) -- View this message in context: http://maven.40175.n5.nabble.com/Parent-SNAPSHOT-not-resolved-Maven-2-2-1-3-0-4-Nexus-repo-tp5772374p5772386.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
