Wayne, Ok thanks. I appreciate the clarification. Right now I have those settings in my company's super pom as I like to call it.
Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 7:19 PM To: Maven Users List Subject: Re: Internal repository question - stopping repo1 In short, Maven lies to you when you're using mirrors -- this is a known bug. So even when it hits a mirror, it reports Central. If you only have 1 repo in your organization and all projects will use it (on \\buildmachine in your case), then you certainly could move these <repository> etc entries into an activeByDefault profile in settings.xml or a shared/common top-level pom. Wayne On 4/23/08, Daniel King <[EMAIL PROTECTED]> wrote: > Wayne, > > Thanks for the help. Are any of those other settings I have not > needed? As far as best practices should any of those settings be in the > settings.xml file instead of the POM if possible? > > I also noticed this in my build output: > > [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking > for updates from internal > [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking > for updates from central > Downloading: > file://\\buildMachine\repository/org/apache/maven/plugins/maven-clean-pl > ugin/2.2/maven-clean-plugin-2.2.pom > 3K downloaded > > So even though it only went to my internal server, I find it strange > that it still states it checked for updates from central. I'm assuming > maybe that info prints out before a check is made to see if it needs to > hit the central repo and it didn't. > > Thanks, > Daniel King > Vurv > > The information contained in this message may be privileged and > confidential and protected from disclosure. If the reader of this > message is not the intended recipient, or an employee or agent > responsible for delivering this message to the intended recipient, you > are hereby notified that any dissemination, distribution or copying of > this communication is strictly prohibited. If you have received this > communication in error, please notify me immediately by replying to the > message and deleting it from your computer. Thank you. > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 23, 2008 3:46 PM > To: Maven Users List > Subject: Re: Internal repository question - stopping repo1 > > You need a to set up a mirror pointing to your local repo as a > <mirrorOf>*</mirrorOf> in your settings.xml file, and Maven will only > go to that server for all of its files. > > Wayne > > On 4/23/08, Daniel King <[EMAIL PROTECTED]> wrote: > > I'm using Archiva 1.0.2 and Maven 2.0.9 using JDK 1.6 on Windows XP. > > > > > > > > I've installed Maven on my local machine and Maven and Archiva on a > > development machine (Not sure if Maven is needed on the dev machine > with > > Archiva but I think it is). > > > > > > > > For some reason I clear out my local repository and do a build, I see > > plugins being downloaded from repo1. I thought that those plugins > would > > be downloaded to my internal repository. Then when I clear out the > > local repository and do a build again it would only get those from my > > internal repository. However it is still going out to repo1 for > > plugins. > > > > > > > > In my project's pom.xml I have the following: > > > > > > > > <repositories> > > > > <repository> > > > > <id>internal</id> > > > > <name>Internal Maven > > Repository</name> > > > > <layout>default</layout> > > > > > > <url>file://\\buildMachine\repository</url> > > > > <snapshots> > > > > > <enabled>false</enabled> > > > > </snapshots> > > > > </repository> > > > > </repositories> > > > > <pluginRepositories> > > > > <pluginRepository> > > > > <id>internal</id> > > > > <name>Internal Maven Plugin > > Repository</name> > > > > > > <url>file://\\buildMachine\repository</url> > > > > <layout>default</layout> > > > > <snapshots> > > > > > <enabled>false</enabled> > > > > </snapshots> > > > > <releases> > > > > > > <updatePolicy>never</updatePolicy> > > > > </releases> > > > > </pluginRepository> > > > > </pluginRepositories> > > > > <distributionManagement> > > > > <repository> > > > > <id>internal</id> > > > > <url>file://\\ buildMachine > > \repository</url> > > > > </repository> > > > > <snapshotRepository> > > > > <id>internal</id> > > > > <url>file://\\ buildMachine > > \repository</url> > > > > <uniqueVersion>true</uniqueVersion> > > > > </snapshotRepository> > > > > </distributionManagement> > > > > > > > > I basically need to setup Maven/Archiva as an internal repository on a > > build machine and have no network traffic go beyond that build machine > > ie not going to repo1. So if something isn't on the internal repo > then > > a build smith would go and manually install and bless whatever they > > need. Security doesn't like the idea of going out to remote repos and > > just bringing stuff down. > > > > > > > > So after looking through the archives and reading other posts, I'm > > confused on what I'm doing wrong. I don't fully understand the > > <servers> and <mirrors> tags and if they even matter to me at this > > point. > > > > > > > > > > > > Any help would be appreciated even if it is to tell me to read a > certain > > section of the manual again. > > > > > > > > Thanks, > > > > Daniel King > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
