You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by MATHUS Baptiste <ma...@mipih.fr> on 2008/06/12 13:42:10 UTC
RE : Configure maven not to hit central repository
> De: Wendy Smoak [mailto:wsmoak@gmail.com]
> Date: mer. 11/06/2008 15:23
> À: users@archiva.apache.org
> Objet : Re: Configure maven not to hit central repository
>
> On Tue, Jun 10, 2008 at 6:23 AM, MATHUS Baptiste <ma...@mipih.fr> wrote:
>
> > So, finally, my question is quite simple : is using "central" as the id
> > for custom repository a good or even acceptable practice? If not, what's
> > the best solution to prevent anyone that has the right settings.xml (and
> > no repo conf in their pom.xml) to directly access some external
> > repository?
> >
> > Is there any documentation existing about those principles?
>
> Re-defining the 'central' repo id is recommended, but it doesn't
> completely solve the problem. To really prevent access to external
> repos you'll need to use mirrors.
Alright. Then I think I'm gonna both
* redefine "central" repository so that it hits our archiva proxy +
* add a mirror on "*" to prevent that manually declared
repositories in poms directly hits the specified address,
and that it hits the same archiva proxy instead.
Thanks, Wendy.
-- Baptiste