Am 14.10.2011 01:16 schrieb "Tommy Chheng" <[email protected]>: > > B is the most similar workflow. > > So i have a few remote maven repos i want to use: > i.e. scala-tools.org and sweble, etc. > > I added both of these to my Nexus server as proxy repos. > > In my local settings.xml, i had to add two <server></server> entries. each > with the same set of nexus username/password. > > I would like to avoid having to specify the nexus username/password in every > <server> definition. >
You could define a repository/content group in nexus, add the desired proxy repos to it and set up authentication for the group as if it was a single repository, then configure it in your settings as a regular repo. This is what I'd recommend if you can't do without authentication in place. Another option might be to use the repo group as a <mirror>. See nexus documentation for details (there is an example for setting up nexus as a mirror somewhere at the beginning). Best regards Ansgar > > > On Thu, Oct 13, 2011 at 12:06 PM, Ansgar Konermann < > [email protected]> wrote: > > > Am 13.10.2011 20:57, schrieb Tommy Chheng: > > > The server ids are different because each is a different proxied server. > > > > What exactly do you mean by "each is a different *proxied server*"? > > > > a) I want to deploy to maven repositories on different servers which are > > located outside my organisation, but I have to use my organisation's > > proxy to connect to these > > or > > b) I have a nexus repository manager where I configured various "proxy > > repositories" (so a *proxied server* is the same as a proxied repository > > in your wording). > > or > > c) same as b) but in addition I'd like to be able to deploy to the proxy > > repositories > > > > Ansgar > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > @tommychheng > http://tommy.chheng.com
