Well, for one thing, not all <repositories> in the pom.xml are evil...
Repositories which *only resolve -SNAPSHOT* artifacts are fine... better if you don't need them, but they are fine. I wrote a blog post about whether one should deploy -SNAPSHOTs in the first place: http://developer-blog.cloudbees.com/2012/12/should-you-deploy-snapshots.html My view is that deploying -SNAPSHOTs is something you should only do *if* absolutely necessary. Otherwise don't! But, if you are on an active tip HEAD of development, and some dependent modules are currently -SNAPSHOT, then adding the <repository> entry to the pom for -SNAPSHOTs only (i.e. <releases>false</releases>) will not affect the resolution when the artifact is released, and hence does not bring the complete world of pain onto anyone pulling the released artifact from central. If you are in-house, you should have a proxying MRM and be using <mirrorOf>*</mirrorOf> so <repositories> should not be necessary at all. HTH On 23 January 2013 09:08, Mirko Friedenhagen <mfriedenha...@gmail.com>wrote: > Hello, > > in a lot of threads on the dev and user list, I have read that "thou > shalt not define repositories in your pom" is the way to go. However > http://maven.apache.org/settings.html#Servers reads: > "The repositories for download and deployment are defined by the > repositories and distributionManagement elements of the POM." > > Is this a bug or is there no consensus on this :-)? > > Regards Mirko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
