Proxify many repositories under the same url
Hi all, We're trying to use archiva as a simple maven proxy. We'd like to be able to provide only one url to our developer boxes that would proxify many repositories. For example, we would put http://ourCIserver/archiva/repository/all/ in every single settings.xml maven file. Behind this url, archiva would be able to be proxifying transparently public well-known repositories + corporate files. Here's what I thought I could do : 1/ define one of more remote repositories (like repo1.maven.org/maven2 for example) 2/ define a managed repo called corporate, or so 3/ define a proxy connector that would offer the union of both repositories above under only one URL. In fact, I want to put the remote repo and all this conf inside archiva only. I don't want dev configs to have to be aware that there are n repositories to declare in their settings.xml. Moreover, we really don't want to be forced to update say 30 computer configs if we decide to add another remote repo inside archiva. I hope I'm being understandable. Is there any way to achieve this with archiva or should I stop looking for this feature? Thanks a lot.
Re: Proxify many repositories under the same url
I'm doing exactly that. They key point turned out to be these settings in settings.xml; internal m2repo ** ... * Archiva Mirror Repository http://m2repo/archiva/repository/internal internal On Fri, 2007-11-09 at 14:47 +0100, MATHUS Baptiste wrote: > Hi all, > > We're trying to use archiva as a simple maven proxy. We'd like to be > able to provide only one url to our developer boxes that would proxify > many repositories. > For example, we would put http://ourCIserver/archiva/repository/all/ in > every single settings.xml maven file. > > Behind this url, archiva would be able to be proxifying transparently > public well-known repositories + corporate files. > > Here's what I thought I could do : > 1/ define one of more remote repositories (like repo1.maven.org/maven2 > for example) > 2/ define a managed repo called corporate, or so > 3/ define a proxy connector that would offer the union of both > repositories above under only one URL. > > In fact, I want to put the remote repo and all this conf inside archiva > only. I don't want dev configs to have to be aware that there are n > repositories to declare in their settings.xml. Moreover, we really don't > want to be forced to update say 30 computer configs if we decide to add > another remote repo inside archiva. > > I hope I'm being understandable. > > Is there any way to achieve this with archiva or should I stop looking > for this feature? > > Thanks a lot.
RE: Proxify many repositories under the same url
OK. With the config you're showing, I suppose maven (on the dev machines) always goes through the archiva server? If yes, then this is exactly what I need. I guess we don't need to define the part since we don't have any authentication set. Is it the mirrorOf set to "*" that's important in what you show? And on the archiva side, what did you configure? Ah, I think I get it. Inside the server, you upload the corporate jars and so on inside the "internal" directory you have somewhere and everything that's proxified coming from outside is also put inside this dir? If so, I'll do it if I can't do differently, but I would have prefered to be able to separate public jars and corporate ones in two different directories, but offer them under one single URL. Thanks again. -Message d'origine- De : cbrown [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 novembre 2007 15:04 À : [EMAIL PROTECTED] Objet : Re: Proxify many repositories under the same url I'm doing exactly that. They key point turned out to be these settings in settings.xml; internal m2repo ** ... * Archiva Mirror Repository http://m2repo/archiva/repository/internal internal On Fri, 2007-11-09 at 14:47 +0100, MATHUS Baptiste wrote: > Hi all, > > We're trying to use archiva as a simple maven proxy. We'd like to be > able to provide only one url to our developer boxes that would proxify > many repositories. > For example, we would put http://ourCIserver/archiva/repository/all/ > in every single settings.xml maven file. > > Behind this url, archiva would be able to be proxifying transparently > public well-known repositories + corporate files. > > Here's what I thought I could do : > 1/ define one of more remote repositories (like repo1.maven.org/maven2 > for example) 2/ define a managed repo called corporate, or so 3/ > define a proxy connector that would offer the union of both > repositories above under only one URL. > > In fact, I want to put the remote repo and all this conf inside > archiva only. I don't want dev configs to have to be aware that there > are n repositories to declare in their settings.xml. Moreover, we > really don't want to be forced to update say 30 computer configs if we > decide to add another remote repo inside archiva. > > I hope I'm being understandable. > > Is there any way to achieve this with archiva or should I stop looking > for this feature? > > Thanks a lot.
RE: Proxify many repositories under the same url
Archiva provides a rudimentary user management through the web
interface. I.e., you need to create a user and assign the user roles
that allow read access (Repository Observer) or write access (Repository
Manager). So, you will need the s.
You didn't mention deployment originally. If you want to deploy to
Archiva, you'll need to define repositories in your settings.xml. Here's
what I have;
In Archiva;
3 Managed repositories; "internal", "dev" and "cm".
2 users; "m2repo" is Global Observer, and "dev" Manager,
"cmadmin" is Global Observer, and "cm" Manager,
6 Remote Repositories that are proxy connected to "internal"
In settings.xml; Note that some sections get commented in/out
depending on whether you are a developer or cmadmin.
internal
m2repo
m2repo-public-password
cm
m2repo
m2repo-public-password
dev
m2repo
m2repo-public-password
myProfile
true
cm
CM Maven2 Repo
http://m2repo/archiva/repository/cm
true
false
dev
Development Maven2 Repo
http://m2repo/archiva/repository/dev
true
true
dev
http://m2repo/archiva/repository/dev
*
Archiva Mirror Repository
http://m2repo/archiva/repository/internal
internal
In individual POMs, I use this construct so, developers and cm publish to their
respective repos, without twiddling with the POMS;
${deploy.id}
Archiva M2 Repository
dav:${deploy.url}
--CB
