Return-Path: 
 <archiva-users-return-224-apmail-maven-archiva-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-archiva-users-archive@locus.apache.org
Received: (qmail 40642 invoked from network); 4 Dec 2006 10:31:59 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Dec 2006 10:31:59 -0000
Received: (qmail 42012 invoked by uid 500); 4 Dec 2006 10:32:08 -0000
Delivered-To: apmail-maven-archiva-users-archive@maven.apache.org
Received: (qmail 41913 invoked by uid 500); 4 Dec 2006 10:32:08 -0000
Mailing-List: contact archiva-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:archiva-users-help@maven.apache.org>
List-Unsubscribe: <mailto:archiva-users-unsubscribe@maven.apache.org>
List-Post: <mailto:archiva-users@maven.apache.org>
List-Id: <archiva-users.maven.apache.org>
Reply-To: archiva-users@maven.apache.org
Delivered-To: mailing list archiva-users@maven.apache.org
Received: (qmail 41904 invoked by uid 99); 4 Dec 2006 10:32:08 -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:32:08 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [192.63.108.53] (HELO usbb-lacimss3.unisys.com) (192.63.108.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 02:31:55 -0800
Received: from usbb-lacgw1.lac.uis.unisys.com ([129.226.160.21]) by
 usbb-lacimss3 with InterScan Message Security Suite;
 Mon, 04 Dec 2006 05:31:32 -0500
Received: from usbb-lacgw1.lac.uis.unisys.com ([129.226.160.23]) by
 usbb-lacgw1.lac.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Dec 2006 05:31:31 -0500
Received: from gbmk-eugw2.eu.uis.unisys.com ([129.221.133.27]) by
 usbb-lacgw1.lac.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Dec 2006 05:31:31 -0500
Received: from chthl-exch1.eu.uis.unisys.com ([129.227.196.11]) by
 gbmk-eugw2.eu.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Dec 2006 10:31:30 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proxy settings
Date: Mon, 4 Dec 2006 11:31:28 +0100
Message-ID: 
 <00F91144E6A88F4CADDD90D34C37AE6A01F48E81@chthl-exch1.eu.uis.unisys.com>
In-Reply-To: 
 <OF58F3D8E7.A95797AE-ONC125723A.0037F46E-C125723A.0038AC1D@globnet.ch>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proxy settings
Thread-Index: AccXjbBYVi/T57lMQ6GfwtfZiP4RhgAAJIxA
From: "Mohni, Daniel" <daniel.mohni@ch.unisys.com>
To: <archiva-users@maven.apache.org>
X-OriginalArrivalTime: 04 Dec 2006 10:31:30.0215 (UTC)
 FILETIME=[5C72FB70:01C7178F]
X-Virus-Checked: Checked by ClamAV on apache.org

Hello Aaron

this can be done setting the mirror in settings.xml

 <mirrors>
   <mirror>
     <id>proxy.central</id>
	<mirrorOf>central</mirrorOf>
     	<name>Internal Mirror of central.</name>
	<url>http://archiva/proxy/maven_release</url>
    </mirror>
  </mirrors>

-> if you use proxy in the url then archiva will try to download
   missing artefacts from the proxied repo setup in archiva

	http://archiva/proxy/maven_release
  =20
-> if you use repository in the url then archiva will only be
   a cache provider for your already downloaded artefacts

	http://archiva/repository/maven_release

maven_release is our internal proxy repository...

I don't know if this is still like this in the current daily build
as I didn't tried it...

hth

Daniel

> -----Original Message-----
> From: Aaron.Digulla@Globus.ch [mailto:Aaron.Digulla@Globus.ch]=20
> Sent: Monday, December 04, 2006 11:19 AM
> To: archiva-users@maven.apache.org
> Subject: Proxy settings
>=20
> Hello,
>=20
> We're using maven for internal development. Since the=20
> internet as a whole=20
> and our connection to it especially are not always reliable=20
> (for example,=20
> a new version of a virus checker sometimes starts to block out maven=20
> downloads), we wanted to use Archiva as a local cache of the=20
> central maven=20
> repositories.
>=20
> As it is right now, I have to configure each repository=20
> individually. What=20
> we would prefer is a setting which makes Archiva the default=20
> proxy for=20
> maven so all external connections are made over it.
>=20
> This would allow us to keep local copies of all artefacts so internet=20
> outages wouldn't affect us anymore. Also, we could fix broken=20
> packages=20
> locally. Ideally, there should be two caches: One with stable=20
> version for=20
> development and one which can update itself with the current=20
> versions from=20
> the internet.
>=20
> Is this possible?
>=20
> Regards,
>=20
> --=20
> Aaron Digulla
>=20
>=20