Let me see if I got it: In my pom.xml I have somthing like this below... My repositories will leave the POM and go to the Archive, for exemple? The POM has only the dependecies?
</repositories> <repository> <id>maven2-repository.dev.java.net</id> <name>Java.net Repository for Maven</name> <url>http://download.java.net/maven/2/</url> </repository> <repository> <id>maven2-repository.jboss.org</id> <name>JBoss Maven Repository</name> <url>http://repository.jboss.org/nexus/content/groups/public-jboss</url> </repository> <repository> <id>maven2-repository.primefaces.org</id> <name>PrimeFaces Maven Repository</name> <url>http://repository.primefaces.org</url> </repository> </repositories> Ivo On Thu, Oct 25, 2012 at 12:24 AM, Alberto Ivo <[email protected]> wrote: > Oh, I get it now. > Thak you all for the replies. > I will study one of those MRM. > Thank you very much!!!!!! > > Ivo > > > > On Wed, Oct 24, 2012 at 11:47 PM, Barrie Treloar <[email protected]>wrote: > >> On Thu, Oct 25, 2012 at 10:37 AM, Alberto Ivo <[email protected]> >> wrote: >> > Hello, >> > >> > I have 5 repositories in my pom.xml, and some of these repositories have >> > repeated jar files. >> > >> > My question is: is there a way to know from what repository maven will >> > download the jar file? It will download from both repositories? It will >> > download from the first repository? It will download from the last >> > repository? >> > >> > Thanks in advance. >> > >> > Ivo. >> >> Ivo, you need to search back in the archives about why putting >> repository declarations in pom.xml is a bad idea. >> >> Look especially for the one that is trying to speed up the build process. >> >> Short summary: >> Maven will needless contact all five of your repositories looking for >> artifacts that probably aren't even there. >> This will require a tcp/ip connection for each one and when you have >> large dependencies this can significantly slow down your build. >> Which is why we all recommend putting a Maven Repository Manager (MRM) >> in between you and the rest of the w >> orld. >> >> MRMs have the smarts to know that a repository has already been >> checked for an artifact and doesn't have it. >> They can be configured to blacklist/whitelist artifacts so you dont >> leak your internal development artifact names to external >> repositories, or waste time looking for something that doesn't exist >> at that repo. >> >> As others in this thread have said, asking where an artifact has come >> from wont really help you. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
