best practice is *never* to put <repository> in your pom. best practice is to run a Maven Repository Manager (there are 3 good ones: [in alphabetical order] archivia, artifactory, nexus)
best practice is to have those present a virtual repository that is an aggregate of all the repositories you need. Then in your settings.xml you do <mirror> <id>my-mrm</id> <url>your virtual repository</url> <mirrorOf>*</mirrorOf> </mirror> Then Maven will only use your mirror. Fast builds, reliable builds, reproducible builds, you have control over the infra. Anything else is a path to folly On 3 April 2012 11:55, Bata Degen <[email protected]> wrote: > Hi list, > > I have set up a Java Enterprise project with Maven in Netbeans. The pom.xml > files are organized hierarchically. I have poms for the entire project, for > the ejb, the web and the assembly (ear) part of the project. > > I don't know in which of these many pom files to place my <repository> > elements. > > Shall they be placed in the root pom or in the pom of the particular module > where they are needed or does it make no difference? Is there a best > practice for that? > > Thanks for your advice! > Bata > > --------------------------------------------------------------------- > 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]
