Well we first tried maven-proxy and it didn't work. We had been trying the developer builds every day and none of them worked so I wrote the proxy.
As a matter of coincidence my co-worker has informed me that he got this working today so tomorrow I will take a closer look at the differences (it may be next week as I am currently travelling)... The biggest difference is it has a very nice web interface to add/remove proxies and such... Again as I said when I get a chance to take it for a test ride (hopefully tomorrow) I will let you know... I think either way the proxy idea has alot of legs whether we use my proxy code or maven-proxy and add a few ivy'ish things to it ;-) For example my rather large ivy resolve took 2 minutes and now with the proxy takes 3 seconds so I can go back to doing an ivy-resolve on every build :-D rather than doing a retrieve to a lib directory and reusing the lib directory... Of course if the cache's on the proxy timeout the resolve takes about 20 seconds... On 12/27/06, Xavier Hanin <[EMAIL PROTECTED]> wrote:
This is interesting. And how does it compare to maven-proxy: http://maven-proxy.codehaus.org/ ? Xavier On 12/27/06, Glen Marchesani <[EMAIL PROTECTED]> wrote: > > I have never used/configured squid so please forgive any > mis-understandings > I may have... Generally the proxy I have is very specific to Ivy/Maven > repositories... > > I think the major differences is the proxy server will proxy multiple > repositories to make it look like one. Also retry timeouts can be set per > repository. I think an example will explain it clearly... I have the > following repositories with their timeout values > > snapshot-builds (0 seconds) > company repo (5 minutes) > ibiblio (1 day) > ivy repo (1 day) > java.net maven repo (1 day) > > When ivy makes a request the proxy will look to see if the request can be > handled with the cached files first if not it will go through the server > list seeing if it can satisfy the request with that server. If a request > to > a server fails with a 404 (file not found) it is marked and won't be > retried > for the set timeout period. If a server is down for any reason it will > get > temporary blacklisted so the builds won't stop. > > With the proxy server I have a single entry to point to the proxy server > in > my ivyconf. Where before I had the proxy server I had all those as > resolver's in the ivyconf. > > Hope that helps... > > > > On 12/27/06, Gilles Scokart <[EMAIL PROTECTED]> wrote: > > > > What are the features of your proxy compared to a generic http proxy > like > > squid? > > > > It's just to satistfy my own curiosity. I currently only use filebased > > repositories because they are easier to manage. And when I want to use > an > > external dependency, I preffer to copy/create it manually on the company > > repository. > > > > > > Gilles > > > > > > > -----Original Message----- > > > From: Glen Marchesani [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, December 27, 2006 3:59 PM > > > To: [email protected] > > > Subject: ivy/maven proxy server > > > > > > Hi Everyone, > > > I recently wrote a proxy server webapp to proxy several > > > remote repositories. It was made for a customer who is using > > > Maven but I am > > > testing it today and it works great with ivy too. It works well and > > > greatly increases responsiveness (especially when ibibilio is > > > acting up). > > > Is anyone interested in this? Has anyone already done > > > something like this? > > > Should this be on the dev/user list? > > > > > > anyways share your thoughts and ideas... > > > > > > -G > > > > > > > > >
