Hi,
the issue is fxed and released. Please try it!
The current release relies on the following solution:
Repositories are divided into groups (String repo.getGroupId()).
Repositories IN the same groups are merged, otherwise they are spoofed
(as before).
The ordering of reposes are still
Tamás Cservenák wrote:
Hi,
Not quite. Proximity is (almost) plain HTTP proxy, but IT DOES have
knowledge about maven reposes (see repository browsing or the use of
?repositoryId=central URL parameter.), but only as separate storages.
What it does not have is STATE, it cannot distuingish the
Hi,
On 7/26/06, Trygve Laugstøl [EMAIL PROTECTED] wrote:
That is not the problem, the problem is that the metadata from all the
repositories has to be _merged_ and dispatched properly by proximity.
That is why any plain http proxy will fail acting as a repository for Maven.
Ah, I see. My
Tamás Cservenák wrote:
Hi,
On 7/26/06, Trygve Laugstøl [EMAIL PROTECTED] wrote:
That is not the problem, the problem is that the metadata from all the
repositories has to be _merged_ and dispatched properly by proximity.
That is why any plain http proxy will fail acting as a repository for
Hi,
I created 3 issues:
http://trac.abstracthorizon.org/proximity/ticket/3
http://trac.abstracthorizon.org/proximity/ticket/17
http://trac.abstracthorizon.org/proximity/ticket/18
and before a few days already got a ticket with similar request:
http://trac.abstracthorizon.org/proximity/ticket/16
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
On 7/25/06, Allison, Bob [EMAIL PROTECTED] wrote:
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
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
: 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
Hi,
Not quite. Proximity is (almost) plain HTTP proxy, but IT DOES have
knowledge about maven reposes (see repository browsing or the use of
?repositoryId=central URL parameter.), but only as separate storages.
What it does not have is STATE, it cannot distuingish the two consecutive
HTTP GET
Just to add:
a planned feature of Proximity (awaited for RC2, but my every day job is
pressing me lately) would be repository relocation.
Behind the curtains, this feature would be implemented just by prefixing
the repository namespace within Proximity, like:
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
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
13 matches
Mail list logo
