On 18 January 2011 09:25, Stephen Connolly <[email protected]> wrote: > On 18 January 2011 09:08, jeb001 <[email protected]> wrote: >> >> ok... If I try to sum up... >> >> First issue was to use a groups URL of nexus.. ok, it's correct now. > > Correct > >> Then, both of the distMgt tag and repository set the same URL.. > > Incorrect... > > distMgt should point to the repo. repositories should point to the > group that aggregates the repo and central and whatever other repos > you want. > >> but >> repositories tag have to >> be moved in the settings.xml. > > It's optional to move it, but its best practice... in fact better > practice is just to use a <mirrorOf>*</mirrorOf> and not have any > repositories in your settings.xml
Just to clarify: If you have repositories in your pom.xml then every build which needs to check for artifacts will check central and all the repositories listed in your pom... that is two web requests and the request to central will be first, slowing down your build and increasing your bandwidth bills... when you change your infrastructure, any projects depending on the old deployed pom will gain an extra invalid url to check against and you will have to wait for that to time-out during a build... so this gives the slowest build If you have repositories in your settings.xml you still get multiple repositories but at least you can update invalid urls and remove having to wait for the timeout If you use <mirrorOf>*</mirrorOf> in your settings.xml then you only ever have one respoitory queried during your build.... so this gives the fastest builds... also mirrorOf handles both pluginRepositories and repositories reducing xml verbage > >> >> Am I right now ? >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
