From ivy-user-return-206-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Thu Dec 28 14:38:52 2006 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 4854 invoked from network); 28 Dec 2006 14:38:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Dec 2006 14:38:51 -0000 Received: (qmail 87245 invoked by uid 500); 28 Dec 2006 14:38:58 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 87227 invoked by uid 500); 28 Dec 2006 14:38:58 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 87218 invoked by uid 99); 28 Dec 2006 14:38:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2006 06:38:58 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gdmlist@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2006 06:38:49 -0800 Received: by ug-out-1314.google.com with SMTP id y2so4831995uge for ; Thu, 28 Dec 2006 06:38:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=Y0lZwLBcynJQnSArq38r/XbDkQQ7ODe1Q2t44CN8c67D3zMaIFFE5at4FmQcPOKco3FR33Sjg5A97hs5zxKlJb92DO77GSPPxakLY93jcHrIAgMTVoP36EhAHVmO9K7I6i6nzwNzTXbj6Sl3nmu5PID1JTNF4J1VccTdP5IzBoQ= Received: by 10.78.180.16 with SMTP id c16mr3765808huf.1167316707668; Thu, 28 Dec 2006 06:38:27 -0800 (PST) Received: by 10.78.155.10 with HTTP; Thu, 28 Dec 2006 06:38:27 -0800 (PST) Message-ID: <96b2ec3f0612280638n5229eb54ucfdf222ff11eed29@mail.gmail.com> Date: Thu, 28 Dec 2006 09:38:27 -0500 From: "Glen Marchesani" Reply-To: glenlist@model3.net To: ivy-user@incubator.apache.org Subject: Re: ivy/maven proxy server In-Reply-To: <96b2ec3f0612271643k102e958btc5ecb68649f07269@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_108292_32211420.1167316707605" References: <1CCEA1ACF736B749B6FEE53168A6BF0001ACFC51@server1e> <007d01c729c8$ca97c310$3020a8c0@isabelteam.be> <96b2ec3f0612270748q690e9f65qd8772d5056a53210@mail.gmail.com> <635a05060612271024w58d45205x57524f30b9e54643@mail.gmail.com> <96b2ec3f0612271643k102e958btc5ecb68649f07269@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_108292_32211420.1167316707605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Okay here is an update we now have archiva http://maven.apache.org/archiva/working. What is archiva you say? Well archiva is the new maven-proxy. You may also hear it called the maven repository manager. These three are all the same thing and that thing is now called archiva... It is a nice simple app to let you configure the proxy server via a webapp. It can proxy to multiple repositories and make them look like a single one. It has one severe drawkback and that is it doesn't do any directory listings so any latest strategies will fail when using it. So this makes it currently unusable for my ivy uses. Though I am going to take a look at the code to see if I can make an ivy friendly version since the webapp based configuration and the look and feel is better than what I did. What I did will aggregate directory listings from multiple servers so in open source tradition I will see if I can easily implement that in archiva and if they are willing to take the contribution (the latter is usually the harder case)... I will let you all know how it goes.... cheers, Glen On 12/27/06, Glen Marchesani wrote: > > > 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 wrote: > > > > This is interesting. And how does it compare to maven-proxy: > > http://maven-proxy.codehaus.org/ ? > > > > Xavier > > > > On 12/27/06, Glen Marchesani 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 < gscokart@gmail.com> 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:gdmlist@gmail.com] > > > > > Sent: Wednesday, December 27, 2006 3:59 PM > > > > > To: ivy-user@incubator.apache.org > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > ------=_Part_108292_32211420.1167316707605--