Thanks Roland. So I guess this means I'm overloading central with my internal (proxied) repostiory instead of denoting a mirror for it? I don't see any difference logically speaking, but I understand that the implementation could be vastly different.
In any case with this change M2Eclipse-0.0.11 doesn't loop inifinitely downloading sources, but its does seem to downlaod rthose sources it can find 39 times each. It repeats this 39 times: 28/05/07 15:05:16: Downloading Repository[central|http://zosma.oz.hubbub.com.au:8080/proximity/reposito ry/release]/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2-sources.jar.sha1 Followed by this 39 times: 28/05/07 15:05:16: Downloaded Repository[central|http://zosma.oz.hubbub.com.au:8080/proximity/reposito ry/release]/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2-sources.jar.sha1 William -----Original Message----- From: Roland Klein [mailto:[EMAIL PROTECTED] Sent: Friday, 25 May 2007 6:05 PM To: user@m2eclipse.codehaus.org Subject: [***POSSIBLE SPAM***] - Re: [m2eclipse-user] RE: [***POSSIBLE SPAM***] - Re: [m2eclipse-user] Infinite loop downloading dependencies - Email found in subject - Email found in subject Hi Wiliam, William Ferguson schrieb: > Sorry Roland, I don't follow. Maybe cause its Friday afternoon. > Indeed two hours to weekend :-)) > I have a single mirror for central defined in > $MAVE_NHOME$\conf\settings.xml that points to a Proximity Server that > is proxying central as well as a couple of other repositories. > > If I remove that mirror then it will attempt to hit central directly > right? > I posted a possible solution earlier here: http://www.nabble.com/forum/ViewPost.jtp?post=10284989&framed=y There you find a skeleton settings.xml, the profile section is important because there you can overwrite the standard setting for central repo. Regardless of the plugin version you're using, i recommend to edit ~\.m2\settings.xml, because this file is used by mvn cli version and also by the eclipse plugin (0.0.10 and 0.0.11). To overwrite the standard central repo has another advantage, some maven plugins define different repo ID's in their pom's (like apache.snapshots, codehaus.org, snapshots.codehaus.org etc.), so if you're central repo url point to you're proxy this plugins will be resolved also because mvn tries as a fallback to resolve dependencies from central and this points to you're proxy. And everything is working ;) We use the same config here, and we can use maven from CLI and in eclipse. Roland > But then I'll need to define another repository that points to my > Proximity Server? > > Can anyone confirm whether this relates to > http://jira.codehaus.org/browse/WAGON-73 and if so whether the change > that has been applied actually fixies the issue? > > William > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
