Downloading Apache Maven Repositories : Proxy Workaround

This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged.  If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission and its attachments without reading or saving in any manner.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

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
update Archiva before the demo, of course, but then you can delete
~/.m2/repository and show Maven auto-downloading from the Archiva repo
etc.

Wayne

On 4/7/08, Edward Song <Edward.Song@...> wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Thanks Wayne for your reply,

They're super strict with their networking and only allow HTTP traffic
through a firewall and the demo computer is onsite.  So installs can only be
done from an internal approved resource.  

Despite their tight restrictions, they have a manual build process, and need
some way to demonstrate that loosening the restriction via Maven and
Archiva, would be a good solution for them.  

My current plan is to use Archiva on a laptop and bring it in to the client
site, which works great by the way.  But this is an instance, where a build
with the most up to date snapshots would be beneficial.

I guess my query is, of installing an internal repository by default,
without looking towards an external repository at all for the initial
snapshots?  

Thanks,
Edward Song

-----Original Message-----
From: Wayne Fay [mailto:waynefay@...]
Sent: Monday, April 07, 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 locally (on the same laptop that
you're demo'ing Maven with). That sounds easiest to me. You'll want to
update Archiva before the demo, of course, but then you can delete
~/.m2/repository and show Maven auto-downloading from the Archiva repo
etc.

Wayne

On 4/7/08, Edward Song <Edward.Song@...> wrote:
> For demo purposes, I wanted to show the benefits of Apache Maven to a few
> others.
>
>
>
> There is a firewall and proxy over here that will not allow Maven to go
get
> artifacts from the central maven repository and the networking guy will
not
> provide the necessary authentication info to allow Maven to tunnel through
> the proxy.
>
>
>
> Is there a way to get an install of Maven which contains the latest
artifact
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...




This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged.  If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission and its attachments without reading or saving in any manner.  Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

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 artifacts you need. You can then clear your local repository to show
how Maven downloads the artifacts from "central"

 

From: Edward Song [mailto:Edward.Song@...]
Sent: Monday, April 07, 2008 3:53 PM
To: users@...
Subject: Downloading Apache Maven Repositories : Proxy Workaround

 

For demo purposes, I wanted to show the benefits of Apache Maven to a
few others.

 

There is a firewall and proxy over here that will not allow Maven to go
get artifacts from the central maven repository and the networking guy
will not provide the necessary authentication info to allow Maven to
tunnel through the proxy.

 

Is there a way to get an install of Maven which contains the latest
artifact snapshots by default?  

 

Looking for a quick fix.

 

Thanks in advance.  Ed

 

Well, for the record, this is the same with a default Archiva
installation. Each to their own :)

On 08/04/2008, Brian E. Fox <brianf@...> wrote:

--
Brett Porter
Blog: http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

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. Artifactory is using about ~50mb. On a server
this might not be important, but on a developer machine that could be
significant. In fact I never thought much about it, but we are running
the public nexus instance[1] that is hosting the proxy and repositories
for our two CI systems and the M2eclipse build, with the JDK default of
64mb of ram.


[1]http://repository.sonatype.org

-----Original Message-----
From: Brett Porter [mailto:brett.porter@...]
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. Each to their own :)

On 08/04/2008, Brian E. Fox <brianf@...> 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 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 artifacts you need. You can then clear your local repository to
show go
>  get artifacts from the central maven repository and the networking
guy

--
Brett Porter
Blog: http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

On 09/04/2008, Brian E. Fox <brianf@...> 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. Artifactory is using about ~50mb. On a server
>  this might not be important, but on a developer machine that could be
>  significant. In fact I never thought much about it, but we are running
>  the public nexus instance[1] that is hosting the proxy and repositories
>  for our two CI systems and the M2eclipse build, with the JDK default of
>  64mb of ram.

Not really the right forum to debate such a thing, but I question your
results since I run with -Xmx64m in the wrapper also, continuously on
my macbook. It's true that the use of JSP and the default of Derby
incurs some overhead which is why I expect that Archiva's figures are
closer to that of Artifactory's.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...