I am using nexus. If you have not already received it, I did send a mail out saying that this seems to be a problem with the m2eclipse plugin. If I run the build from the command line all artifacts are downloaded from my internal repo. So when you say "reproduce" I can only do so using the m2eclipse plugin. I have asked this question on that mailing list also since it does not seem to be a maven core problem. But if you could still provide some light on the issue, I of course would be appeciative ;-).
--- Todd Thiessen -----Original Message----- From: Rafael Trestini [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2008 1:11 PM To: Maven Users List Subject: Re: Using an internal central repository without changing settings.xml Todd, Before I'm try to reproduce your scenerio, let me know: how do you populate your central repository? Are you using repository managers like nexus or archiva? Rafael On Tue, Nov 11, 2008 at 3:52 PM, Todd Thiessen <[EMAIL PROTECTED]> wrote: > This looks like a problem with the m2eclipse plugin I am using. Doing > the build from the command line downloads only from my central repo. > > --- > Todd Thiessen > > >> _____________________________________________ >> From: Thiessen, Todd (BVW:9T16) >> Sent: Tuesday, November 11, 2008 12:27 PM >> To: 'users@maven.apache.org' >> Subject: Using an internal central repository without changing >> settings.xml >> >> I have been looking into this for a couple of days and can't find the >> answer. I suspect it isn't possible but I think it will be best to >> ask those who can tell me definitively. >> >> I want to be able to define a project which only has access to an >> internally defined repository. Note I said project not user. Using >> the settings.xml to define my interal repository as the mirror to >> external ones I don't think is the right thing to do. Doing this >> makes the project unportable since all developers on the project >> would have to share the same settings.xml file. Bad mojo. >> >> I have tried modifying my POM file such that it overrides the central >> repo... like this: >> >> <repositories> >> <repository> >> <id>central</id> >> <url>http://myinteralrepo</url> >> </repository> >> </repositories> >> <pluginRepositories> >> <pluginRepository> >> <id>central</id> >> <url>http://myinteralrepo</url> >> </pluginRepository> >> </pluginRepositories> >> >> However, this does not seem to be sufficient. Most dependencies are >> coming from my local repo but not all and I can't figure out why some >> are not. Here is a snippet of maven output. >> >> url = http://myinteralrepo >> Downloading: >> http://myinteralrepo/org/apache/maven/plugins/maven-resources-plugin/ >> 2 >> .2/maven-resources-plugin-2.2.pom >> url = http://repo1.maven.org/maven2 >> Downloading: >> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/ >> 1 >> /maven-plugins-1.pom >> 3K downloaded >> url = http://repo1.maven.org/maven2 >> Downloading: >> http://repo1.maven.org/maven2/org/apache/maven/maven-parent/1/maven-p >> a >> rent-1.pom >> 6K downloaded >> >> What is special about the first artifact, >> maven-resources-pluggin-2.2, such that it comes from my internal repo >> but the others come from maven central? >> >> The only way that I have been completely successful in ensuring that >> all artifacts come from my internal repo is by making the appropriate >> changes to my settings.xml file. But as I have already mentioned, I >> don't wish to do this. >> >> Thoughts? >> >> >> --- >> Todd Thiessen >> > -- Responsibility is the price of freedom --------------------------------------------------------------------- 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]
