Proximity does only use the first metadata that is found in the list of sources. If central is defined first, it ALWAYS wins and you get release metadata by default.
In this case, however, it found metadata for a plugin in a snapshot repository (it had never been released, so there was no data for it in central). Maven did not know that the metadata came from a snapshot repository (it was just using "central" because nothing else was configured) so when Maven tried to get the POM that went with the metadata it just retrieved it barfed all over itself because central is configured to only serve releases. If MRM, combined with a wildcard mirror in the settings, will allow Maven to retrieve the snapshot properly, then things will be OK. This means that MAVEN has to know the difference between the repositories, which probably means that all of the various repositories need to be configured in the project POM. MRM will probably also need to keep the metadata from each repository separate so that the resulting metadata in the local repository points to the correct remote repository (even though they are all mirrored in the same place). -----Original Message----- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 09:11 To: Maven Developers List Subject: Re: Maven Repository Manager: Will it avoid aggregation of repositories? Allison, Bob wrote: > 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. The problem here is that Proximity is nothing but a plain HTTP proxy and has no knowledge of Maven repositories which falls apart with two repositories with the same metadata file. The first one will probably cached and the latter will never be used. So if the first repository is the snapshot repository and the latter the release repository it will probably never download the release. This is a bit disappointing as Proximity is basically what maven-proxy always has been delivering. -- Trygve --------------------------------------------------------------------- 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]
