+1 Nailed. It's not all black-or-white.
On Fri, Mar 22, 2013 at 10:19 AM, Stephen Connolly < [email protected]> wrote: > > Finally, putting them in your settings.xml allows reacting to repository > location changes when building old builds, putting them in your pom.xml may > mean that 1 year from now, checking out the tag will not build without > modifying the pom.xml (or even worse, depending on the 1 year old version > in a project your are building - you might want to verify a regression in > behaviour for example - won't work because that version's pom.xml has > invalid repository URLs) > > For all the above reasons, pushing OSS projects to central is the > recommended practice, but getting them into any public Maven repository is > better than not having them in a public Maven repository. > > TL;DR pushing open source projects to a repository other than Central (at > least for the moment given how Maven works) is bad practice. Arguing over > whether it is better to reference those other repositories from > settings.xml or from pom.xml is very much like two fleas arguing over who > will get squashed first when the building collapses and flattens the dog > they live on ;-) > >
