Forgive the double post but I can not tell who this bug belongs to!
Or just have everyone install the parent which is a PITA if you have a lot of projects going on with lots of parents.
It looks like a simple bug where the Maven/Nexus interface does not follow the right path after finding out that the parent is not available locally.
Who gets the JIRA entry? Ron On 30/09/2013 4:26 PM, NRO wrote:
Hi Ron, That's exactly what we've got. I work in a large organization with many developers, Jenkins continuous build systems, Nexus, etc... Everyday, teams need to share projects thru the repository and SNAPSHOTS are what everybody uses during development phases. The only workaround I found to sort of fix the problem is to exclude the snapshot repository from the Nexus mirror section and then declare explicitly the Nexus snapshot repository in the repository section of the pom. As shown in a previous post above. nr -- View this message in context: http://maven.40175.n5.nabble.com/Parent-Pom-does-not-work-with-Nexus-tp5714786p5772259.html Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Ron Wheeler President Artifact Software Inc email: [email protected] skype: ronaldmwheeler phone: 866-970-2435, ext 102 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
