No, multiple active proxies doesn't make any sense. The only reason for multiple active ones is possibly to support a different active one per protocol, but I imagine even that would be very infrequent.
- Brett Scokart Gilles wrote: > I'm looking at a the support of the proxies in the site:deploy goal. > > I discovered a few strange things, and I would like to have some explanation > on the proxy support philosophy. > > In maven settings, we have the possibility to define multiple proxies, with > their type (http, socks, etc). The DefaultWagonManager stores a map protocol > -> proxy. By the way, I think the name protocol -> proxy is misleading. It > should be proxy_type -> proxy. > > I also notice that the DefaultMaven (who fill the DefaultWagonManager) only > pass the first active proxy found in the settings. > > So basically, I wonder if maven should really support multiple active > proxies. And if it does, what's the logic behind it? When should we use > which one? > > I think it should be simpler to only allow one proxy active at a time. What > was the rational to have more than one proxy configurable in the settings? > > > Thanks, > > SCOKART Gilles > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
