Below is the message from Wayne I was referring to.  Now that I have downloaded 
and built maven 2.2-RC3, I guess I could put log messages into it to pin-point 
the exact line of code where the proxy fails.  But already as it is,  in 
running maven 2.2-RC3 it already has debug level logging turned on and is 
showing a lot more information than was being shown when this problem started 
occuring when I upgraded from maven 2.0.9 to maven 2.1.  The sad thing is I 
have been keeping this maven proxy problem to myself because we have only been 
using maven for a few months.  If I make it be known that it won't work and 
there is no solution if we upgrade to any version higher than maven 2.0.9,  it 
is likely the managers will ban maven from being used.
--------------------------------------------------

Proxy issues are, by their very nature, almost impossible for an
outsider to investigate and resolve. There are literally hundreds (or
more) of proxy server software packages in the world, and while they
all more or less work for basic web browsing, most have issues with
various pieces of software like Maven.

I won't claim to know all the changes made to the Maven codebase from
2.0.9 to 2.1.0 (much less the changes in supporting utility libraries)
but it would seem that some change has caused your proxy to stop
working. If you seriously want to see this resolved, it will probably
take some effort on your part to get Maven and all its libraries
running in a debugger to try to track down what is different.

Unless a ton of people start complaining about similar problems or the
issue can be tracked to a specific change made in Maven (or a util
library), I don't see this being resolved in any well-defined
timeframe.

So, I'd stick with 2.0.9 for now. Have you tried 2.0.10 yet?

Wayne


----- Original Message ----
From: John Casey <[email protected]>
To: Maven Users List <[email protected]>
Sent: Friday, June 12, 2009 10:38:30 AM
Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3

Can you tell me what Wayne's explanation was for your proxy problem? Or, if 
Wayne's around, maybe he can chime in.

I'm not familiar with this particular discussion, so I'm not sure how to help. 
Proxies can be incredibly hard to debug remotely, when I don't have access to 
probe the running system and find out where things are coming apart.

-john

Robert Glover wrote:
>     
> The proxy error using 2.2.0-RC3 (see email below) was using the binary 
> download. Since then, I've built 2.2.0-RC3 from source and am looking at it 
> in Eclipse.  It builds cleanly if I set it to not test;  however I don't know 
> how to run it (with it pointed to a pom.xml to build), so I'm just looking at 
> the source code).
>     The proxy problem I am having (see email below) is from 
> org.apache.maven.artifact.manager.DefaultWagonManage;  I can't pinpoint the 
> exact line of source code.
>     I cannot really take this further myself, with my level of expertise (or 
> lack there-of), other than to have noticed that something similar to my 
> problem is reported in a Jira that was opened around roughly the same time my 
> problem first started happening. That Jira is:  
> https://issues.sonatype.org/browse/NEXUS-515
>     I sure would be a happy camper if my meager contribution here could 
> motivate someone to figure out how to get my proxy to work.  A solution seems 
> so tantalizingly close.  For example, if I could compare the source code of 
> the 2.0.9 version of DefaultWagManager to the source code version of it in 
> later versions.
> 
> ________________________________
> From: Robert Glover <[email protected] 
> <mailto:[email protected]>>
> To: Maven Users List <[email protected] <mailto:[email protected]>>
> Sent: Thursday, June 11, 2009 6:44:06 PM
> Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3
> 
> 
> I downloaded "apache-maven-2.2.0-RC3" and tried it out but sadly,  I get the 
> same proxy problem I have been getting in all versions of maven subsequent to 
> 2.0.9.  Maven 2.0.9 continues to work fine, but if I change to 2.2.0.RC3 and 
> use the same pom.xml file and the same settings.xml file (where the proxy 
> config is) it  causes a proxy error and I cannot do a "mvn package"
>   Wayne has patiently explained to me that there is nothing to be done about 
> this, I'm simply stuck using maven 2.0.9 forever or until by luck a 
> subsequent release of Maven  mysteriously starts letting my corporate proxy 
> work again.  Sigh.  Below is the console log of my unsuccessful attempt to 
> use 2.2.0-RC3
> 
> C:\JavaLibs\aTestMaven220_rc3_a>set m2
> M2=C:\JavaLibs\apache-maven-2.2.0-RC3\bin
> M2_HOME=C:\JavaLibs\apache-maven-2.2.0-RC3
> 
> C:\JavaLibs\aTestMaven220_rc3_a>cd simple
> 
> C:\JavaLibs\aTestMaven220_rc3_a\simple>dir
> Volume in drive C is COEv2_0
> Volume Serial Number is 1428-1262
> 
> Directory of C:\JavaLibs\aTestMaven220_rc3_a\simple
> 
> 06/11/2009  06:31 PM    <DIR>          .
> 06/11/2009  06:31 PM    <DIR>          ..
> 06/09/2009  12:33 PM              636 pom.xml
> 06/11/2009  06:29 PM    <DIR>          src
>               1 File(s)            636 bytes
>               3 Dir(s)  5,835,960,320 bytes free
> 
> C:\JavaLibs\aTestMaven220_rc3_a\simple>mvn -X package
> + Error stacktraces are turned on.
> Apache Maven 2.2.0-RC3 (r783569; 2009-06-10 19:26:18-0400)
> Java version: 1.5.0_12
> Java home: C:\progfile\Java\jdk1.5.0_12\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and 
> Settings\B1RXGC0\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 
> 'C:\JavaLibs\apache-maven-2.2.0-RC3\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> [DEBUG] Wagons could not be registered as the extension container was never 
> created
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building simple
> [INFO]    task-segment: [package]
> [INFO] 
> ------------------------------------------------------------------------
> [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:12 
> for project: null:maven-resources-plugin:maven-plugin:2.3 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:9 for 
> project: org.apache.maven.plugins:maven-plugins:pom:12 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: 
> org.apache.maven:maven-parent:pom:9 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8 
> for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the 
> repository.
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for 
> project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
> [DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project: 
> org.apache.maven:maven-parent:pom:5 from the repository.
> [DEBUG] Trying repository central
> [DEBUG] Checking for pre-existing User-Agent configuration.
> [DEBUG] Adding User-Agent configuration.
> [DEBUG] Connecting to repository: 'central' with url: 
> 'http://repo1.maven.org/maven2' <http://repo1.maven.org/maven2%27>.
> [DEBUG] Using Proxy: b1web1.frb.org
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> Jun 11, 2009 6:35:12 PM 
> hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost
> WARNING: Required credentials not available for BASIC <any 
> realm>@repo1.maven.org:80
> Jun 11, 2009 6:35:12 PM 
> hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost
> WARNING: Preemptive authentication requested but no default credentials 
> available
> [DEBUG] 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
>  - Status code: 403
> [DEBUG] Access denied to: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> org.apache.maven.wagon.authorization.AuthorizationException: Access denied 
> to: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven
>         at 
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:510)
>         at 
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
>         at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
>         at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:327)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:270)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1539)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1808)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1296)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1260)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:518)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>         at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [WARNING] Unable to get resource 
> 'org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3' from repository 
> central (http://repo1.maven.org/maven2): Authorization fail
> re-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> [DEBUG] Trying repository central
> [DEBUG] Checking for pre-existing User-Agent configuration.
> [DEBUG] Adding User-Agent configuration.
> [DEBUG] Connecting to repository: 'central' with url: 
> 'http://repo1.maven.org/maven2' <http://repo1.maven.org/maven2%27>.
> [DEBUG] Using Proxy: b1web1.frb.org
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> Jun 11, 2009 6:35:13 PM 
> hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost
> WARNING: Required credentials not available for BASIC <any 
> realm>@repo1.maven.org:80
> Jun 11, 2009 6:35:13 PM 
> hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost
> WARNING: Preemptive authentication requested but no default credentials 
> available
> [DEBUG] 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
>  - Status code: 403
> [DEBUG] Access denied to: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> org.apache.maven.wagon.authorization.AuthorizationException: Access denied 
> to: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven
>         at 
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:510)
>         at 
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
>         at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
>         at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:327)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:270)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1539)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1808)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1296)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1260)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:518)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>         at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [WARNING] Unable to get resource 
> 'org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3' from repository 
> central (http://repo1.maven.org/maven2): Authorization fail
> re-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> GroupId: org.apache.maven.plugins
> ArtifactId: maven-surefire-plugin
> Version: 2.4.3
> 
> Reason: Unable to download the artifact from any repository
> 
>   org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build 
> project for plugin 'org.apache.maven.plugins:maven-surefire-plugin': POM 
> 'org.apache.maven.plug
> any repository
> 
>   org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> for project org.apache.maven.plugins:maven-surefire-plugin
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1556)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1808)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1296)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1260)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:518)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>         at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build 
> project for plugin 'org.apache.maven.plugins:maven-surefire-plugin': POM 
> 'org.apache.maven.p
> om any repository
> 
>   org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> for project org.apache.maven.plugins:maven-surefire-plugin
>         at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:286)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1539)
>         ... 19 more
> Caused by: org.apache.maven.project.ProjectBuildingException: POM 
> 'org.apache.maven.plugins:maven-surefire-plugin' not found in repository: 
> Unable to download the arti
> 
>   org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> for project org.apache.maven.plugins:maven-surefire-plugin
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:270)
>         ... 22 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
> Unable to download the artifact from any repository
> 
>   org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> 
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
>         at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
>         ... 24 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
> download the artifact from any repository
>         at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:349)
>         at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
>         ... 26 more
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Thu Jun 11 18:35:13 EDT 2009
> [INFO] Final Memory: 2M/4M
> [INFO] 
> ------------------------------------------------------------------------
> C:\JavaLibs\aTestMaven220_rc3_a\simple>
> 
> 
> 
>  
> 
> 
> 
> ________________________________
> From: John Casey <[email protected] <mailto:[email protected]>>
> To: Maven Users List <[email protected] <mailto:[email protected]>>
> Sent: Thursday, June 11, 2009 2:45:17 PM
> Subject: [PLEASE TEST] Maven 2.2.0-RC3
> 
> Hi,
> 
> I've finally gotten through the assembly plugin release and the mess
> that is POM transformation, and I think we're ready to test another
> Maven 2.2.0 release candidate.
> 
> You can grab this RC here:
> 
> https://repository.apache.org/content/repositories/maven-staging-011/
> 
> The big change here is that POM tranformations have been completely
> backed out of Maven, pending further design discussion to address the
> relevant use cases more thoroughly. Along with this, I've added two new
> pseudo-features for MNG-3203 and MNG-3401. These are documented in:
> 
> <site-trunk>/src/site/apt/guides/mini/guide-default-execution-ids.apt
> 
> Additionally, I've documented the use of Animal Sniffer to ensure
> 1.4-compatible builds under:
> 
> <site-trunk>/src/site/apt/guides/mini/guide-building-jdk14-on-jdk15.apt
> 
> ...this is a stop-gap solution until the compiler plugin supports
> toolchains.
> 
> I haven't published the site with these new documents yet, just in case
> there are some horrible and unforseen problems with what I've done. :-)
> 
> Please give this release candidate a try, and let me know if you run
> into any problems.
> 
> I'll probably let this sit for a couple of days, and if there aren't any
> problems I'll call a vote. Before this is a possibility, though, I'm
> going to need to incorporate the new policies on source-release
> distributions, so I'm just letting you know now that this isn't done yet.
> 
> Thanks, and happy building!
> 
> -john
> 
>     
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to