Use Nexus as a local proxy/cache. You can download and run it out of the
box with no config so it's the easiest and lightest instance to run on a
local machine. Just hook up your Maven to it with a mirrorOf central (or
*) and run your build ahead of time. This will populate Nexus with all
the
, 2008 4:34 PM
To: Maven Users List
Subject: Re: Downloading Apache Maven Repositories : Proxy Workaround
Just connect to the Maven repo before your demo and let it update. You
may want to run with -o for offline so it doesn't try to update again
during the demo.
Or perhaps consider running Archiva
Well, for the record, this is the same with a default Archiva
installation. Each to their own :)
On 08/04/2008, Brian E. Fox [EMAIL PROTECTED] wrote:
Use Nexus as a local proxy/cache. You can download and run it out of the
box with no config so it's the easiest and lightest instance to run on
://repository.sonatype.org
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 10:02 AM
To: Maven Users List
Subject: Re: Downloading Apache Maven Repositories : Proxy Workaround
Well, for the record, this is the same with a default Archiva
installation
On 09/04/2008, Brian E. Fox [EMAIL PROTECTED] wrote:
Since you mentioned it, and I wasn't aware that there was a standalone
archiva, I decided to check it out. Firing it up with no config, just
adding an admin user uses up ~130MB of ram. A standalone default Nexus
config is using only ~28.
Just connect to the Maven repo before your demo and let it update. You
may want to run with -o for offline so it doesn't try to update again
during the demo.
Or perhaps consider running Archiva locally (on the same laptop that
you're demo'ing Maven with). That sounds easiest to me. You'll want to
