Something else of note I discovered using Proximity: If you have multiple repositories mirrored, you need to keep the snapshot repositories away from the release repositories. In my case, I was using Proximity to mirror "central" but it also had several other repositories in its configuration including a couple snapshot repositories. My original thinking was that I could do this and avoid needing to specify individual repositories in my master POM. The problem with this arrangement is that if Proximity returns metadata for a snapshot release, Maven will be unable to retrieve the artifact and POM because central is defined as releases only.
I don't know if this problem would be eliminated by using the new global mirror setting that will be coming out in 2.0.5 or not. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 23:42 To: Maven Developers List Subject: Re: Maven Repository Manager: Will it avoid aggregation of repositories? Hi Barrie, While the current implementation is aggregating them, I'll keep this in mind when I review it in the next couple of days. It's probably best to keep the repositories separate, but to have a single index for the rest of the operations so it can appear as an aggregate (and be able to access a "view" over the aggregate from certain URLs). - Brett On 25/07/2006 1:37 PM, Barrie Treloar wrote: > I just stumbled into a feature of maven-proxy which caused me some > problems. > > Assume you have three repositories defined in your maven-proxy: A, B and C. > > In your pom you have specified the repository A and in your settings > have configured A to point to your maven-proxy installation. Because > maven-proxy aggregates the repositories the artifacts from the B and C > repositories are available even though you have not defined them in > your pom. > > Normally this would not show up as an issue. The problem manifests as > soon as you start using SNAPSHOT version of artifacts, perhaps as part > of doing some work on maven itself. Due to the aggregation you will > find that you are using SNAPSHOT versions instead of the more stable > released versions. > > My workaround was to not put SNAPSHOT repositories into your > maven-proxy configuration and to create a separate maven-proxy > installation that just contains the SNAPSHOTS. > > I think maven-proxy should have used the repository id as part of the > mirror URL so that aggregation was never a side effect. So something > like: > http://maven-proxy:9999/central/.... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
