You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Barrie Treloar <ba...@gmail.com> on 2007/08/03 05:21:56 UTC
Proxying internal repositories?
The proxy connector only allows linking an internal repository with a
remote repository.
At the moment I have our repositories physically separated on disk (a
hang over from maven-proxy setup)
I have the following layout:
* internal
* internal_snapshot
* maven_proxy
I would like to keep these repositories separate as I want to be able
to clean up the internal ones (delete out of date snapshots, etc)
To keep this setup I need to have three proxy definitions in my
~/.m2/settings.xml. I'd prefer one. Since two of them are release
repositories it will mean mvn will contact both internal and
maven_proxy, which thanks to blacklists is very fast.
This does make the proxy setup a little more complicated than:
<mirror>
<id>maven-proxy</id>
<name>Maven-Proxy Mirror</name>
<url>http://HOST:PORT/archiva/repository/maven_proxy</url>
<mirrorOf>*</mirrorOf>
</mirror>
Is what I am doing a valid use case?
Do others have a similar need?
Am I going about this in the wrong way?
I'd appreciate other peoples thoughts.
Cheers
Re: Proxying internal repositories?
Posted by Barrie Treloar <ba...@gmail.com>.
On 8/24/07, Brett Porter <br...@gmail.com> wrote:
> Hi Barrie,
>
> Sorry I missed your earlier post. I think this is a valid use case.
>
> With the changes I'm making for MRM-462, it should be again possible
> to proxy file:// repositories, though I think even with the current
> release you could configure the available http:// URL for each of your
> repositories. The downside is that you need to configure a "remote"
> repository that corresponds to each of your internal ones.
remote repo is a valid workaround.
My internal repositories are already exposed via http.
Thanks
Re: Proxying internal repositories?
Posted by Brett Porter <br...@gmail.com>.
Hi Barrie,
Sorry I missed your earlier post. I think this is a valid use case.
With the changes I'm making for MRM-462, it should be again possible
to proxy file:// repositories, though I think even with the current
release you could configure the available http:// URL for each of your
repositories. The downside is that you need to configure a "remote"
repository that corresponds to each of your internal ones.
I think it would be worth considering a new feature post-1.0 that can
better map a virtual repository over the top of separate managed ones.
Cheers,
Brett
On 24/08/07, Barrie Treloar <ba...@gmail.com> wrote:
> On 8/3/07, Barrie Treloar <ba...@gmail.com> wrote:
> > The proxy connector only allows linking an internal repository with a
> > remote repository.
> >
> > At the moment I have our repositories physically separated on disk (a
> > hang over from maven-proxy setup)
> >
> > I have the following layout:
> > * internal
> > * internal_snapshot
> > * maven_proxy
> >
> > I would like to keep these repositories separate as I want to be able
> > to clean up the internal ones (delete out of date snapshots, etc)
> >
> > To keep this setup I need to have three proxy definitions in my
> > ~/.m2/settings.xml. I'd prefer one. Since two of them are release
> > repositories it will mean mvn will contact both internal and
> > maven_proxy, which thanks to blacklists is very fast.
> >
> > This does make the proxy setup a little more complicated than:
> > <mirror>
> > <id>maven-proxy</id>
> > <name>Maven-Proxy Mirror</name>
> > <url>http://HOST:PORT/archiva/repository/maven_proxy</url>
> > <mirrorOf>*</mirrorOf>
> > </mirror>
> >
> > Is what I am doing a valid use case?
> > Do others have a similar need?
> > Am I going about this in the wrong way?
> >
> > I'd appreciate other peoples thoughts.
>
> No one else has a similar setup/problems/thoughts?
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
Re: Proxying internal repositories?
Posted by Barrie Treloar <ba...@gmail.com>.
On 8/3/07, Barrie Treloar <ba...@gmail.com> wrote:
> The proxy connector only allows linking an internal repository with a
> remote repository.
>
> At the moment I have our repositories physically separated on disk (a
> hang over from maven-proxy setup)
>
> I have the following layout:
> * internal
> * internal_snapshot
> * maven_proxy
>
> I would like to keep these repositories separate as I want to be able
> to clean up the internal ones (delete out of date snapshots, etc)
>
> To keep this setup I need to have three proxy definitions in my
> ~/.m2/settings.xml. I'd prefer one. Since two of them are release
> repositories it will mean mvn will contact both internal and
> maven_proxy, which thanks to blacklists is very fast.
>
> This does make the proxy setup a little more complicated than:
> <mirror>
> <id>maven-proxy</id>
> <name>Maven-Proxy Mirror</name>
> <url>http://HOST:PORT/archiva/repository/maven_proxy</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
>
> Is what I am doing a valid use case?
> Do others have a similar need?
> Am I going about this in the wrong way?
>
> I'd appreciate other peoples thoughts.
No one else has a similar setup/problems/thoughts?