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]
