Re: Dramatically speed up dependency resolution

2008-01-28 Thread Tom Huybrechts
I just tried it out and sometimes got this error halfway through a build: Exception in thread pool-101-thread-2 java.lang.ArrayIndexOutOfBoundsException: 10 at java.util.ArrayList.add(ArrayList.java:352) at

Re: Dramatically speed up dependency resolution

2008-01-28 Thread Don Brown
On 1/28/08, Tom Huybrechts [EMAIL PROTECTED] wrote: I just tried it out and sometimes got this error halfway through a build: Doh, forgot to synchronize the resolved and missing artifact lists, now that they can be accessed by multiple threads. I put up a new version (has that and a few pool

Re: Dramatically speed up dependency resolution

2008-01-28 Thread Tom Huybrechts
Did you build this on java 6? I'm getting bad class version errors on java 5: + Error stacktraces are turned on. - this realm = plexus.core urls[0] = file:/c:/dev/tools/maven/lib/maven-2.0.9-SNAPSHOT-uber.jar Number of imports: 0

Re: Dramatically speed up dependency resolution

2008-01-28 Thread Jason van Zyl
Also I will look when you have some tests as I was about to look and glad Tom tried it. On 28-Jan-08, at 3:42 AM, Don Brown wrote: On 1/28/08, Tom Huybrechts [EMAIL PROTECTED] wrote: I just tried it out and sometimes got this error halfway through a build: Doh, forgot to synchronize the

Dramatically speed up dependency resolution

2008-01-27 Thread Don Brown
One of my pain points with Maven is how slow it is to download the internet, so rather than bitch (or more accurately, continue bitching), I decided to do something about it. I created a customized build of Maven 2 (MNG-3379, WAGON-98) that, at least in my simple tests, cut the dependency

Re: Dramatically speed up dependency resolution

2008-01-27 Thread Don Brown
On 1/28/08, Jason van Zyl [EMAIL PROTECTED] wrote: * Connection pooling: Uses the http wagon instead of http-lightweight and fixed incorrect http client initialization James Dumay also worked on this. So you might want to talk to him or look. I'm not sure if you're the Don Brown from

RE: Dramatically speed up dependency resolution

2008-01-27 Thread Brian E. Fox
Is it absolutely required to use 1.5? If there's a good way to work around it, we should aim for 2.0.9 -Original Message- From: Don Brown [mailto:[EMAIL PROTECTED] Sent: Sunday, January 27, 2008 4:49 PM To: Maven Developers List Subject: Re: Dramatically speed up dependency resolution

Re: Dramatically speed up dependency resolution

2008-01-27 Thread Don Brown
way to work around it, we should aim for 2.0.9 -Original Message- From: Don Brown [mailto:[EMAIL PROTECTED] Sent: Sunday, January 27, 2008 4:49 PM To: Maven Developers List Subject: Re: Dramatically speed up dependency resolution On 1/28/08, Jason van Zyl [EMAIL PROTECTED] wrote

Re: Dramatically speed up dependency resolution

2008-01-27 Thread Jesse McConnell
4:49 PM To: Maven Developers List Subject: Re: Dramatically speed up dependency resolution On 1/28/08, Jason van Zyl [EMAIL PROTECTED] wrote: * Connection pooling: Uses the http wagon instead of http-lightweight and fixed incorrect http client initialization James Dumay also

Re: Dramatically speed up dependency resolution

2008-01-27 Thread Jason van Zyl
should aim for 2.0.9 -Original Message- From: Don Brown [mailto:[EMAIL PROTECTED] Sent: Sunday, January 27, 2008 4:49 PM To: Maven Developers List Subject: Re: Dramatically speed up dependency resolution On 1/28/08, Jason van Zyl [EMAIL PROTECTED] wrote: * Connection pooling: Uses the http