Return-Path: Delivered-To: apmail-maven-archiva-users-archive@locus.apache.org Received: (qmail 36737 invoked from network); 4 Dec 2006 10:19:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2006 10:19:28 -0000 Received: (qmail 17311 invoked by uid 500); 4 Dec 2006 10:19:36 -0000 Delivered-To: apmail-maven-archiva-users-archive@maven.apache.org Received: (qmail 17267 invoked by uid 500); 4 Dec 2006 10:19:36 -0000 Mailing-List: contact archiva-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: archiva-users@maven.apache.org Delivered-To: mailing list archiva-users@maven.apache.org Received: (qmail 17258 invoked by uid 99); 4 Dec 2006 10:19:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 02:19:36 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [212.249.5.50] (HELO mailsw2.globus.ch) (212.249.5.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 02:19:24 -0800 Received: from v0c132ns.gknet.ch (V0C132NS [172.18.2.55]) by mailsw2.globus.ch (Clearswift SMTPRS 5.2.5) with ESMTP id for ; Mon, 4 Dec 2006 11:19:02 +0100 To: archiva-users@maven.apache.org Subject: Proxy settings MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5 September 26, 2003 Message-ID: From: Aaron.Digulla@Globus.ch Date: Mon, 4 Dec 2006 11:19:00 +0100 X-MIMETrack: Serialize by Router on V0C132NS/Globus-Gruppe(Release 6.5.4FP2|September 12, 2005) at 04.12.2006 11:19:02, Serialize complete at 04.12.2006 11:19:02 Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked by ClamAV on apache.org Hello, We're using maven for internal development. Since the internet as a whole and our connection to it especially are not always reliable (for example, a new version of a virus checker sometimes starts to block out maven downloads), we wanted to use Archiva as a local cache of the central maven repositories. As it is right now, I have to configure each repository individually. What we would prefer is a setting which makes Archiva the default proxy for maven so all external connections are made over it. This would allow us to keep local copies of all artefacts so internet outages wouldn't affect us anymore. Also, we could fix broken packages locally. Ideally, there should be two caches: One with stable version for development and one which can update itself with the current versions from the internet. Is this possible? Regards, -- Aaron Digulla