You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Dix <Jo...@amdocs.com> on 2013/09/06 20:09:30 UTC
RE: Failure to find artifact in Nexus
+ maven dev team..
-----Original Message-----
From: John Dix
Sent: Friday, September 06, 2013 11:08 AM
To: Maven Users List; rwheeler@artifact-software.com
Subject: RE: Failure to find artifact in Nexus
Let me rephrase this. It is finding it in the repository we have it in (3rdparty), but when it gets to http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases, which is where the artifact ISN'T, maven says "Oops. I can't find it I give up" and craps out DESPITE the fact that it has already found it and downloaded the file.
-----Original Message-----
From: John Dix
Sent: Friday, September 06, 2013 10:59 AM
To: Maven Users List; rwheeler@artifact-software.com
Subject: RE: Failure to find artifact in Nexus
Yes it is. It downloads the file. I have verified it is in the .m2 repository on the drive where the build is located. When I execute a second time it bypasses the error.
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Thursday, September 05, 2013 6:49 PM
To: users@maven.apache.org
Subject: Re: Failure to find artifact in Nexus
Is the artifact
commons-httpclient:commons-httpclient:jar:3.1
in the http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases repo?
That will split your problem in half.
Ron
On 05/09/2013 8:17 PM, John Dix wrote:
> Mark: We are going to our own Nexus repository:
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>
> -----Original Message-----
> From: Mark Eggers [mailto:its_toasted@yahoo.com]
> Sent: Thursday, September 05, 2013 5:03 PM
> To: Maven Users List
> Subject: Re: Failure to find artifact in Nexus
>
> On 9/5/2013 4:47 PM, John Dix wrote:
>> Hello everyone,
>>
>> I have hit a wall in trying to figure out why we're getting this failure:
>>
>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>> find commons-httpclient:commons-httpclient:jar:3.1 in
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s was cached in the local repository, resolution will not be
>> reattempted until the update interval of qpass-nexus-hosted-releases
>> has elapsed or updates are forced
>>
>> during our builds. On a clean .m2/repository directory(ran rm -rf ~/.m2/repository/*) and executing the following command:
>>
>> mvn -e -DskipTests clean install -f <path to our pom>. This happens the first time and then after that it picks up the file. It happens on the SAME file everytime after a wiping of the .ms/repository directory. I have looked and visually verified that the jar file it is looking for is in the .m2 repo and is the correct version it is looking for. I have tried using the -U switch with the maven command to no avail. We are getting this on one more jar file after this one gets resolved but it behaves the same: rerun and it finds it. We do not encounter this on other products, just this one.
>>
>> Does anyone have any idea on how to move forward on this? I am at a loss.
>>
>> Regards!
>> -Caolan.
>>
>> Maven essentials:
>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>> arch: "amd64", family: "unix"
>>
>>
>> Full Stack:
>> [ERROR] Failed to execute goal on project
>> applicationContextComponents: Could not resolve dependencies for
>> project
>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0
>> -
>> rc-4-SNAPSHOT: Failure to find
>> commons-httpclient:commons-httpclient:jar:3.1 in
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s was cached in the local repository, resolution will not be
>> reattempted until the update interval of qpass-nexus-hosted-releases
>> has elapsed or updates are forced -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project applicationContextComponents: Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:601)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>> 3
>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>> Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>> ... 22 more
>> Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>> ... 23 more
>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>> ... 24 more
>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>> at
>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def
>> a
>> ultArtifactResolver.java:427)
>>
>> John "Caolan" Dix
>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>> Division
>> o: 206-288-0334 m: 425.351.7340
> Why is Maven looking in the "releases" repository on Nexus?
>
> I would expect it to be looking at either public (if you use the group), or the mirror of central.
>
> . . . just my naive two cents.
> /mde/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
https://jira.codehaus.org/browse/MNG-5181 ... The use of the MAVEN_OPTS flag has resolved this issue for us. However now it is telling us that maven-clean-plugin 2.5 cannot be found in our release repository. This might be an ancillary issue as we have not encountered this before until I used the workaround given in the Jira bug.
Also, that bug feels like a hack to a problem that is a bug in the code. https://jira.codehaus.org/browse/MNG-5185 seems to point towards working offline or over a VPN is a cause however that is not the case for us. I feel that this is a bug in the code. Once it finds the artifact, it should not keep looking for it, and then fail later. Is it possible that this is still under investigation elsewhere and that I can follow it? I think that this needs follow-up and further investigation rather than just tell my 3.1 system to act like it's 2.x. if that's the solution, why should I upgrade ay all?
-----Original Message-----
From: John Dix
Sent: Monday, September 09, 2013 10:44 AM
To: Maven Developers List
Subject: RE: Failure to find artifact in Nexus
I am deleting the .m2/repository (rm -rf ~/.m2/repository/*) before every build.
I have used the -U before as well.
-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Monday, September 09, 2013 10:41 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus
Well, it is actually not a bug, but a more strict behavior of Maven 3 compared to Maven 2.
The issue is a solution to get the Maven 2 behavior with Maven 3.
In short: Maven 3 tries to predict if the project can still be built with an empty repository, even if the dependencies are available in your local repository.
It could be that for some reason your local repository got corrupt.
Have you tried to remove the commons-httpclient folder and build the project again ( with -U to force an update?). You should be fine, since these files should exist at the Nexus repository.
Robert
Op Mon, 09 Sep 2013 19:29:09 +0200 schreef John Dix <Jo...@amdocs.com>:
> Still repro's in Maven 3.1. The bug says it is fixed there if I am
> reading it correctly. However, the artifact is stored in Nexus in
> exactly where we want it: 3rdparty. Maven pulls it down, and rather
> than acknowledge it's existence in the local .m2 repository, it
> continues to try and find it and then dies when it cannot locate. Is
> this the same thing? The bug doesn't read like it is. Bear in mind I
> am mostly new to Maven and still getting used to the lingo.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Monday, September 09, 2013 10:05 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> In that case you're probably hitting
> https://jira.codehaus.org/browse/MNG-5181
>
> Robert
>
> Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix
> <Jo...@amdocs.com>:
>
>> What I mean by being "downloaded" is that it is easily found in the
>> local .m2 repository of the machine maven is being executed on.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Monday, September 09, 2013 9:44 AM
>> To: Maven Developers List
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Thanks!
>>
>> The problem is not that I am not getting the artifact because I am.
>> The problem is that Maven acts like it doesn't have the file(after
>> downloading it) and then exits. If I rerun the build it passes just
>> fine. It does this on very specific artifacts every time. It is very
>> reproducible. What I am trying to find out is why it is doing this so
>> that I can correct the behaviour.
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> Sent: Saturday, September 07, 2013 10:02 AM
>> To: Maven Developers List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> hi,
>>
>> /nexus/content/repositories/releases should be used for releases of
>> your company or project /nexus/content/repositories/thirdparty should
>> be used for ... third party artifacts.
>>
>> Developers should connect to a repository-*group* instead of a
>> repository-*host*, so the Nexus administrator can control which
>> hosted and proxied repositories should be available for them (on URL
>> to rule them all).
>> Normally this would be the .../public repository
>>
>> What I don't understand is what you mean with the file being downloaded.
>> Maven always comes with 2 lines:
>> Downloading .... which mean it will *try* to download this file
>> Downloaded .... means that Maven succeeded.
>> If you don't see the second line, then it is not downloaded.
>> I guess that confused you a bit.
>>
>> Robert
>>
>> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
>> <Jo...@amdocs.com>:
>>
>>> + maven dev team..
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 11:08 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Let me rephrase this. It is finding it in the repository we have it
>>> in (3rdparty), but when it gets to
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s , which is where the artifact ISN'T, maven says "Oops. I can't
>>> find it I give up" and craps out DESPITE the fact that it has
>>> already found it and downloaded the file.
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 10:59 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Yes it is. It downloads the file. I have verified it is in the .m2
>>> repository on the drive where the build is located. When I execute a
>>> second time it bypasses the error.
>>>
>>> -----Original Message-----
>>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>>> Sent: Thursday, September 05, 2013 6:49 PM
>>> To: users@maven.apache.org
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>>
>>> Is the artifact
>>>
>>> commons-httpclient:commons-httpclient:jar:3.1
>>>
>>> in the
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e
>>> s
>>> repo?
>>>
>>> That will split your problem in half.
>>>
>>> Ron
>>>
>>> On 05/09/2013 8:17 PM, John Dix wrote:
>>>> Mark: We are going to our own Nexus repository:
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s
>>>> e
>>>> s
>>>>
>>>> -----Original Message-----
>>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>>> Sent: Thursday, September 05, 2013 5:03 PM
>>>> To: Maven Users List
>>>> Subject: Re: Failure to find artifact in Nexus
>>>>
>>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I have hit a wall in trying to figure out why we're getting this
>>>>> failure:
>>>>>
>>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>
>>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>>> ~/.m2/repository/*) and executing the following command:
>>>>>
>>>>> mvn -e -DskipTests clean install -f <path to our pom>. This
>>>>> happens the first time and then after that it picks up the file.
>>>>> It happens on the SAME file everytime after a wiping of the
>>>>> .ms/repository directory. I have looked and visually verified that
>>>>> the jar file it is looking for is in the .m2 repo and is the
>>>>> correct version it is looking for. I have tried using the -U
>>>>> switch with the maven command to no avail. We are getting this on
>>>>> one more jar file after this one gets resolved but it behaves the
>>>>> same: rerun and it finds it. We do not encounter this on other products, just this one.
>>>>>
>>>>> Does anyone have any idea on how to move forward on this? I am at
>>>>> a loss.
>>>>>
>>>>> Regards!
>>>>> -Caolan.
>>>>>
>>>>> Maven essentials:
>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>>> arch: "amd64", family: "unix"
>>>>>
>>>>>
>>>>> Full Stack:
>>>>> [ERROR] Failed to execute goal on project
>>>>> applicationContextComponents: Could not resolve dependencies for
>>>>> project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>>> 0
>>>>> -
>>>>> rc-4-SNAPSHOT: Failure to find
>>>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
>>>>> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal on project applicationContextComponents: Could not
>>>>> resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>>> 3
>>>>> 52) Caused by:
>>>>> org.apache.maven.project.DependencyResolutionException:
>>>>> Could not resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>>>> ... 22 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>>>> ... 23 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.ArtifactResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>>>> ... 24 more
>>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(
>>>>> D
>>>>> e
>>>>> f
>>>>> a
>>>>> ultArtifactResolver.java:427)
>>>>>
>>>>> John "Caolan" Dix
>>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>>>> Division
>>>>> o: 206-288-0334 m: 425.351.7340
>>>> Why is Maven looking in the "releases" repository on Nexus?
>>>>
>>>> I would expect it to be looking at either public (if you use the
>>>> group), or the mirror of central.
>>>>
>>>> . . . just my naive two cents.
>>>> /mde/
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>> This message and the information contained herein is proprietary
>>>> and confidential and subject to the Amdocs policy statement, you
>>>> may review at http://www.amdocs.com/email_disclaimer.asp
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and
>>> confidential and subject to the Amdocs policy statement, you may
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
I am deleting the .m2/repository (rm -rf ~/.m2/repository/*) before every build.
I have used the -U before as well.
-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Monday, September 09, 2013 10:41 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus
Well, it is actually not a bug, but a more strict behavior of Maven 3 compared to Maven 2.
The issue is a solution to get the Maven 2 behavior with Maven 3.
In short: Maven 3 tries to predict if the project can still be built with an empty repository, even if the dependencies are available in your local repository.
It could be that for some reason your local repository got corrupt.
Have you tried to remove the commons-httpclient folder and build the project again ( with -U to force an update?). You should be fine, since these files should exist at the Nexus repository.
Robert
Op Mon, 09 Sep 2013 19:29:09 +0200 schreef John Dix <Jo...@amdocs.com>:
> Still repro's in Maven 3.1. The bug says it is fixed there if I am
> reading it correctly. However, the artifact is stored in Nexus in
> exactly where we want it: 3rdparty. Maven pulls it down, and rather
> than acknowledge it's existence in the local .m2 repository, it
> continues to try and find it and then dies when it cannot locate. Is
> this the same thing? The bug doesn't read like it is. Bear in mind I
> am mostly new to Maven and still getting used to the lingo.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Monday, September 09, 2013 10:05 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> In that case you're probably hitting
> https://jira.codehaus.org/browse/MNG-5181
>
> Robert
>
> Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix
> <Jo...@amdocs.com>:
>
>> What I mean by being "downloaded" is that it is easily found in the
>> local .m2 repository of the machine maven is being executed on.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Monday, September 09, 2013 9:44 AM
>> To: Maven Developers List
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Thanks!
>>
>> The problem is not that I am not getting the artifact because I am.
>> The problem is that Maven acts like it doesn't have the file(after
>> downloading it) and then exits. If I rerun the build it passes just
>> fine. It does this on very specific artifacts every time. It is very
>> reproducible. What I am trying to find out is why it is doing this so
>> that I can correct the behaviour.
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> Sent: Saturday, September 07, 2013 10:02 AM
>> To: Maven Developers List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> hi,
>>
>> /nexus/content/repositories/releases should be used for releases of
>> your company or project /nexus/content/repositories/thirdparty should
>> be used for ... third party artifacts.
>>
>> Developers should connect to a repository-*group* instead of a
>> repository-*host*, so the Nexus administrator can control which
>> hosted and proxied repositories should be available for them (on URL
>> to rule them all).
>> Normally this would be the .../public repository
>>
>> What I don't understand is what you mean with the file being downloaded.
>> Maven always comes with 2 lines:
>> Downloading .... which mean it will *try* to download this file
>> Downloaded .... means that Maven succeeded.
>> If you don't see the second line, then it is not downloaded.
>> I guess that confused you a bit.
>>
>> Robert
>>
>> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
>> <Jo...@amdocs.com>:
>>
>>> + maven dev team..
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 11:08 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Let me rephrase this. It is finding it in the repository we have it
>>> in (3rdparty), but when it gets to
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s , which is where the artifact ISN'T, maven says "Oops. I can't
>>> find it I give up" and craps out DESPITE the fact that it has
>>> already found it and downloaded the file.
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 10:59 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Yes it is. It downloads the file. I have verified it is in the .m2
>>> repository on the drive where the build is located. When I execute a
>>> second time it bypasses the error.
>>>
>>> -----Original Message-----
>>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>>> Sent: Thursday, September 05, 2013 6:49 PM
>>> To: users@maven.apache.org
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>>
>>> Is the artifact
>>>
>>> commons-httpclient:commons-httpclient:jar:3.1
>>>
>>> in the
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e
>>> s
>>> repo?
>>>
>>> That will split your problem in half.
>>>
>>> Ron
>>>
>>> On 05/09/2013 8:17 PM, John Dix wrote:
>>>> Mark: We are going to our own Nexus repository:
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s
>>>> e
>>>> s
>>>>
>>>> -----Original Message-----
>>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>>> Sent: Thursday, September 05, 2013 5:03 PM
>>>> To: Maven Users List
>>>> Subject: Re: Failure to find artifact in Nexus
>>>>
>>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I have hit a wall in trying to figure out why we're getting this
>>>>> failure:
>>>>>
>>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>
>>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>>> ~/.m2/repository/*) and executing the following command:
>>>>>
>>>>> mvn -e -DskipTests clean install -f <path to our pom>. This
>>>>> happens the first time and then after that it picks up the file.
>>>>> It happens on the SAME file everytime after a wiping of the
>>>>> .ms/repository directory. I have looked and visually verified that
>>>>> the jar file it is looking for is in the .m2 repo and is the
>>>>> correct version it is looking for. I have tried using the -U
>>>>> switch with the maven command to no avail. We are getting this on
>>>>> one more jar file after this one gets resolved but it behaves the
>>>>> same: rerun and it finds it. We do not encounter this on other products, just this one.
>>>>>
>>>>> Does anyone have any idea on how to move forward on this? I am at
>>>>> a loss.
>>>>>
>>>>> Regards!
>>>>> -Caolan.
>>>>>
>>>>> Maven essentials:
>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>>> arch: "amd64", family: "unix"
>>>>>
>>>>>
>>>>> Full Stack:
>>>>> [ERROR] Failed to execute goal on project
>>>>> applicationContextComponents: Could not resolve dependencies for
>>>>> project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>>> 0
>>>>> -
>>>>> rc-4-SNAPSHOT: Failure to find
>>>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
>>>>> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal on project applicationContextComponents: Could not
>>>>> resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>>> 3
>>>>> 52) Caused by:
>>>>> org.apache.maven.project.DependencyResolutionException:
>>>>> Could not resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>>>> ... 22 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>>>> ... 23 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.ArtifactResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>>>> ... 24 more
>>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(
>>>>> D
>>>>> e
>>>>> f
>>>>> a
>>>>> ultArtifactResolver.java:427)
>>>>>
>>>>> John "Caolan" Dix
>>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>>>> Division
>>>>> o: 206-288-0334 m: 425.351.7340
>>>> Why is Maven looking in the "releases" repository on Nexus?
>>>>
>>>> I would expect it to be looking at either public (if you use the
>>>> group), or the mirror of central.
>>>>
>>>> . . . just my naive two cents.
>>>> /mde/
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>> This message and the information contained herein is proprietary
>>>> and confidential and subject to the Amdocs policy statement, you
>>>> may review at http://www.amdocs.com/email_disclaimer.asp
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and
>>> confidential and subject to the Amdocs policy statement, you may
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Robert Scholte <rf...@apache.org>.
Well, it is actually not a bug, but a more strict behavior of Maven 3
compared to Maven 2.
The issue is a solution to get the Maven 2 behavior with Maven 3.
In short: Maven 3 tries to predict if the project can still be built with
an empty repository, even if the dependencies are available in your local
repository.
It could be that for some reason your local repository got corrupt.
Have you tried to remove the commons-httpclient folder and build the
project again ( with -U to force an update?). You should be fine, since
these files should exist at the Nexus repository.
Robert
Op Mon, 09 Sep 2013 19:29:09 +0200 schreef John Dix <Jo...@amdocs.com>:
> Still repro's in Maven 3.1. The bug says it is fixed there if I am
> reading it correctly. However, the artifact is stored in Nexus in
> exactly where we want it: 3rdparty. Maven pulls it down, and rather than
> acknowledge it's existence in the local .m2 repository, it continues to
> try and find it and then dies when it cannot locate. Is this the same
> thing? The bug doesn't read like it is. Bear in mind I am mostly new to
> Maven and still getting used to the lingo.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Monday, September 09, 2013 10:05 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> In that case you're probably hitting
> https://jira.codehaus.org/browse/MNG-5181
>
> Robert
>
> Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix
> <Jo...@amdocs.com>:
>
>> What I mean by being "downloaded" is that it is easily found in the
>> local .m2 repository of the machine maven is being executed on.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Monday, September 09, 2013 9:44 AM
>> To: Maven Developers List
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Thanks!
>>
>> The problem is not that I am not getting the artifact because I am.
>> The problem is that Maven acts like it doesn't have the file(after
>> downloading it) and then exits. If I rerun the build it passes just
>> fine. It does this on very specific artifacts every time. It is very
>> reproducible. What I am trying to find out is why it is doing this so
>> that I can correct the behaviour.
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> Sent: Saturday, September 07, 2013 10:02 AM
>> To: Maven Developers List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> hi,
>>
>> /nexus/content/repositories/releases should be used for releases of
>> your company or project /nexus/content/repositories/thirdparty should
>> be used for ... third party artifacts.
>>
>> Developers should connect to a repository-*group* instead of a
>> repository-*host*, so the Nexus administrator can control which hosted
>> and proxied repositories should be available for them (on URL to rule
>> them all).
>> Normally this would be the .../public repository
>>
>> What I don't understand is what you mean with the file being downloaded.
>> Maven always comes with 2 lines:
>> Downloading .... which mean it will *try* to download this file
>> Downloaded .... means that Maven succeeded.
>> If you don't see the second line, then it is not downloaded.
>> I guess that confused you a bit.
>>
>> Robert
>>
>> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
>> <Jo...@amdocs.com>:
>>
>>> + maven dev team..
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 11:08 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Let me rephrase this. It is finding it in the repository we have it
>>> in (3rdparty), but when it gets to
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s , which is where the artifact ISN'T, maven says "Oops. I can't find
>>> it I give up" and craps out DESPITE the fact that it has already
>>> found it and downloaded the file.
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 10:59 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Yes it is. It downloads the file. I have verified it is in the .m2
>>> repository on the drive where the build is located. When I execute a
>>> second time it bypasses the error.
>>>
>>> -----Original Message-----
>>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>>> Sent: Thursday, September 05, 2013 6:49 PM
>>> To: users@maven.apache.org
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>>
>>> Is the artifact
>>>
>>> commons-httpclient:commons-httpclient:jar:3.1
>>>
>>> in the
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s
>>> repo?
>>>
>>> That will split your problem in half.
>>>
>>> Ron
>>>
>>> On 05/09/2013 8:17 PM, John Dix wrote:
>>>> Mark: We are going to our own Nexus repository:
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> e
>>>> s
>>>>
>>>> -----Original Message-----
>>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>>> Sent: Thursday, September 05, 2013 5:03 PM
>>>> To: Maven Users List
>>>> Subject: Re: Failure to find artifact in Nexus
>>>>
>>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I have hit a wall in trying to figure out why we're getting this
>>>>> failure:
>>>>>
>>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>
>>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>>> ~/.m2/repository/*) and executing the following command:
>>>>>
>>>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>>>> the first time and then after that it picks up the file. It happens
>>>>> on the SAME file everytime after a wiping of the .ms/repository
>>>>> directory. I have looked and visually verified that the jar file it
>>>>> is looking for is in the .m2 repo and is the correct version it is
>>>>> looking for. I have tried using the -U switch with the maven
>>>>> command to no avail. We are getting this on one more jar file after
>>>>> this one gets resolved but it behaves the same: rerun and it finds
>>>>> it. We do not encounter this on other products, just this one.
>>>>>
>>>>> Does anyone have any idea on how to move forward on this? I am at a
>>>>> loss.
>>>>>
>>>>> Regards!
>>>>> -Caolan.
>>>>>
>>>>> Maven essentials:
>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>>> arch: "amd64", family: "unix"
>>>>>
>>>>>
>>>>> Full Stack:
>>>>> [ERROR] Failed to execute goal on project
>>>>> applicationContextComponents: Could not resolve dependencies for
>>>>> project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>>> 0
>>>>> -
>>>>> rc-4-SNAPSHOT: Failure to find
>>>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s e s was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
>>>>> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal on project applicationContextComponents: Could not
>>>>> resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>>> at
>>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>>> 3
>>>>> 52) Caused by:
>>>>> org.apache.maven.project.DependencyResolutionException:
>>>>> Could not resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>>>> ... 22 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>>>> at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>>>> ... 23 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.ArtifactResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>>>> ... 24 more
>>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>>> s es was cached in the local repository, resolution will not be
>>>>> reattempted until the update interval of
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>>>> at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(D
>>>>> e
>>>>> f
>>>>> a
>>>>> ultArtifactResolver.java:427)
>>>>>
>>>>> John "Caolan" Dix
>>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>>>> Division
>>>>> o: 206-288-0334 m: 425.351.7340
>>>> Why is Maven looking in the "releases" repository on Nexus?
>>>>
>>>> I would expect it to be looking at either public (if you use the
>>>> group), or the mirror of central.
>>>>
>>>> . . . just my naive two cents.
>>>> /mde/
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>> This message and the information contained herein is proprietary and
>>>> confidential and subject to the Amdocs policy statement, you may
>>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and
>>> confidential and subject to the Amdocs policy statement, you may
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Laird Nelson <lj...@gmail.com>.
On Mon, Sep 9, 2013 at 10:29 AM, John Dix <Jo...@amdocs.com> wrote:
> Still repro's in Maven 3.1. The bug says it is fixed there if I am reading
> it correctly. However, the artifact is stored in Nexus in exactly where we
> want it: 3rdparty. Maven pulls it down, and rather than acknowledge it's
> existence in the local .m2 repository, it continues to try and find it and
> then dies when it cannot locate. Is this the same thing? The bug doesn't
> read like it is. Bear in mind I am mostly new to Maven and still getting
> used to the lingo.
>
I've been working with Maven for years and occasionally get errors like
this.
Go into your local repository under the appropriate directory tree and look
for a file named _maven.repositories. Delete it (I have no idea what it
does; never bothered to figure out what it's for; it is regenerated as
appropriate). I hate resorting to black magic but this often fixes errors
of this type.
The other possibility is that the file itself is one of those insidious ISP
HTML files that get served up in response to bad DNS requests. Some ISPs
(as often found in coffee shops) will, when you attempt to connect to a
private network or some other resource that can't be found, instead of
serving up a 404 as they should will instead serve up a 200 and give you an
HTML page back. To Maven, this looks like a successful request: you asked
for foo.jar, the site said 200, so Maven saves a hunk of HTML into your
local repository and names it foo.jar. This problem can usually be avoided
by going to the ISP in question with a mob armed with torches and
pitchforks and telling them to get their house in order. If that fails,
tell your boss that VPN connectivity is not working, and so consequently
you have no choice but to go {fishing,skiing,clubbing,parasailing} and
you'll be back once connectivity is restored.
Best,
Laird
--
http://about.me/lairdnelson
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
Still repro's in Maven 3.1. The bug says it is fixed there if I am reading it correctly. However, the artifact is stored in Nexus in exactly where we want it: 3rdparty. Maven pulls it down, and rather than acknowledge it's existence in the local .m2 repository, it continues to try and find it and then dies when it cannot locate. Is this the same thing? The bug doesn't read like it is. Bear in mind I am mostly new to Maven and still getting used to the lingo.
-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Monday, September 09, 2013 10:05 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus
In that case you're probably hitting
https://jira.codehaus.org/browse/MNG-5181
Robert
Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix <Jo...@amdocs.com>:
> What I mean by being "downloaded" is that it is easily found in the
> local .m2 repository of the machine maven is being executed on.
>
> -----Original Message-----
> From: John Dix
> Sent: Monday, September 09, 2013 9:44 AM
> To: Maven Developers List
> Subject: RE: Failure to find artifact in Nexus
>
> Thanks!
>
> The problem is not that I am not getting the artifact because I am.
> The problem is that Maven acts like it doesn't have the file(after
> downloading it) and then exits. If I rerun the build it passes just
> fine. It does this on very specific artifacts every time. It is very
> reproducible. What I am trying to find out is why it is doing this so
> that I can correct the behaviour.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Saturday, September 07, 2013 10:02 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> hi,
>
> /nexus/content/repositories/releases should be used for releases of
> your company or project /nexus/content/repositories/thirdparty should
> be used for ... third party artifacts.
>
> Developers should connect to a repository-*group* instead of a
> repository-*host*, so the Nexus administrator can control which hosted
> and proxied repositories should be available for them (on URL to rule
> them all).
> Normally this would be the .../public repository
>
> What I don't understand is what you mean with the file being downloaded.
> Maven always comes with 2 lines:
> Downloading .... which mean it will *try* to download this file
> Downloaded .... means that Maven succeeded.
> If you don't see the second line, then it is not downloaded.
> I guess that confused you a bit.
>
> Robert
>
> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
> <Jo...@amdocs.com>:
>
>> + maven dev team..
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Friday, September 06, 2013 11:08 AM
>> To: Maven Users List; rwheeler@artifact-software.com
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Let me rephrase this. It is finding it in the repository we have it
>> in (3rdparty), but when it gets to
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s , which is where the artifact ISN'T, maven says "Oops. I can't find
>> it I give up" and craps out DESPITE the fact that it has already
>> found it and downloaded the file.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Friday, September 06, 2013 10:59 AM
>> To: Maven Users List; rwheeler@artifact-software.com
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Yes it is. It downloads the file. I have verified it is in the .m2
>> repository on the drive where the build is located. When I execute a
>> second time it bypasses the error.
>>
>> -----Original Message-----
>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>> Sent: Thursday, September 05, 2013 6:49 PM
>> To: users@maven.apache.org
>> Subject: Re: Failure to find artifact in Nexus
>>
>>
>> Is the artifact
>>
>> commons-httpclient:commons-httpclient:jar:3.1
>>
>> in the
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s
>> repo?
>>
>> That will split your problem in half.
>>
>> Ron
>>
>> On 05/09/2013 8:17 PM, John Dix wrote:
>>> Mark: We are going to our own Nexus repository:
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e
>>> s
>>>
>>> -----Original Message-----
>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>> Sent: Thursday, September 05, 2013 5:03 PM
>>> To: Maven Users List
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>> Hello everyone,
>>>>
>>>> I have hit a wall in trying to figure out why we're getting this
>>>> failure:
>>>>
>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s e s was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>
>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>> ~/.m2/repository/*) and executing the following command:
>>>>
>>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>>> the first time and then after that it picks up the file. It happens
>>>> on the SAME file everytime after a wiping of the .ms/repository
>>>> directory. I have looked and visually verified that the jar file it
>>>> is looking for is in the .m2 repo and is the correct version it is
>>>> looking for. I have tried using the -U switch with the maven
>>>> command to no avail. We are getting this on one more jar file after
>>>> this one gets resolved but it behaves the same: rerun and it finds
>>>> it. We do not encounter this on other products, just this one.
>>>>
>>>> Does anyone have any idea on how to move forward on this? I am at a
>>>> loss.
>>>>
>>>> Regards!
>>>> -Caolan.
>>>>
>>>> Maven essentials:
>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>> arch: "amd64", family: "unix"
>>>>
>>>>
>>>> Full Stack:
>>>> [ERROR] Failed to execute goal on project
>>>> applicationContextComponents: Could not resolve dependencies for
>>>> project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>> 0
>>>> -
>>>> rc-4-SNAPSHOT: Failure to find
>>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s e s was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
>>>> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal on project applicationContextComponents: Could not
>>>> resolve dependencies for project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>> at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>> at
>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>> at
>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>> at
>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>> at
>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>> 3
>>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>>> Could not resolve dependencies for project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>> at
>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>>> ... 22 more
>>>> Caused by:
>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>>> at
>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>>> ... 23 more
>>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>>> ... 24 more
>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of
>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(D
>>>> e
>>>> f
>>>> a
>>>> ultArtifactResolver.java:427)
>>>>
>>>> John "Caolan" Dix
>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>>> Division
>>>> o: 206-288-0334 m: 425.351.7340
>>> Why is Maven looking in the "releases" repository on Nexus?
>>>
>>> I would expect it to be looking at either public (if you use the
>>> group), or the mirror of central.
>>>
>>> . . . just my naive two cents.
>>> /mde/
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and
>>> confidential and subject to the Amdocs policy statement, you may
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Robert Scholte <rf...@apache.org>.
In that case you're probably hitting
https://jira.codehaus.org/browse/MNG-5181
Robert
Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix <Jo...@amdocs.com>:
> What I mean by being "downloaded" is that it is easily found in the
> local .m2 repository of the machine maven is being executed on.
>
> -----Original Message-----
> From: John Dix
> Sent: Monday, September 09, 2013 9:44 AM
> To: Maven Developers List
> Subject: RE: Failure to find artifact in Nexus
>
> Thanks!
>
> The problem is not that I am not getting the artifact because I am. The
> problem is that Maven acts like it doesn't have the file(after
> downloading it) and then exits. If I rerun the build it passes just
> fine. It does this on very specific artifacts every time. It is very
> reproducible. What I am trying to find out is why it is doing this so
> that I can correct the behaviour.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Saturday, September 07, 2013 10:02 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> hi,
>
> /nexus/content/repositories/releases should be used for releases of your
> company or project /nexus/content/repositories/thirdparty should be used
> for ... third party artifacts.
>
> Developers should connect to a repository-*group* instead of a
> repository-*host*, so the Nexus administrator can control which hosted
> and proxied repositories should be available for them (on URL to rule
> them all).
> Normally this would be the .../public repository
>
> What I don't understand is what you mean with the file being downloaded.
> Maven always comes with 2 lines:
> Downloading .... which mean it will *try* to download this file
> Downloaded .... means that Maven succeeded.
> If you don't see the second line, then it is not downloaded.
> I guess that confused you a bit.
>
> Robert
>
> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
> <Jo...@amdocs.com>:
>
>> + maven dev team..
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Friday, September 06, 2013 11:08 AM
>> To: Maven Users List; rwheeler@artifact-software.com
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Let me rephrase this. It is finding it in the repository we have it in
>> (3rdparty), but when it gets to
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>> , which is where the artifact ISN'T, maven says "Oops. I can't find it
>> I give up" and craps out DESPITE the fact that it has already found it
>> and downloaded the file.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Friday, September 06, 2013 10:59 AM
>> To: Maven Users List; rwheeler@artifact-software.com
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Yes it is. It downloads the file. I have verified it is in the .m2
>> repository on the drive where the build is located. When I execute a
>> second time it bypasses the error.
>>
>> -----Original Message-----
>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>> Sent: Thursday, September 05, 2013 6:49 PM
>> To: users@maven.apache.org
>> Subject: Re: Failure to find artifact in Nexus
>>
>>
>> Is the artifact
>>
>> commons-httpclient:commons-httpclient:jar:3.1
>>
>> in the
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>> repo?
>>
>> That will split your problem in half.
>>
>> Ron
>>
>> On 05/09/2013 8:17 PM, John Dix wrote:
>>> Mark: We are going to our own Nexus repository:
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s
>>>
>>> -----Original Message-----
>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>> Sent: Thursday, September 05, 2013 5:03 PM
>>> To: Maven Users List
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>> Hello everyone,
>>>>
>>>> I have hit a wall in trying to figure out why we're getting this
>>>> failure:
>>>>
>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> e s was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>>
>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>> ~/.m2/repository/*) and executing the following command:
>>>>
>>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>>> the first time and then after that it picks up the file. It happens
>>>> on the SAME file everytime after a wiping of the .ms/repository
>>>> directory. I have looked and visually verified that the jar file it
>>>> is looking for is in the .m2 repo and is the correct version it is
>>>> looking for. I have tried using the -U switch with the maven command
>>>> to no avail. We are getting this on one more jar file after this one
>>>> gets resolved but it behaves the same: rerun and it finds it. We do
>>>> not encounter this on other products, just this one.
>>>>
>>>> Does anyone have any idea on how to move forward on this? I am at a
>>>> loss.
>>>>
>>>> Regards!
>>>> -Caolan.
>>>>
>>>> Maven essentials:
>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>> arch: "amd64", family: "unix"
>>>>
>>>>
>>>> Full Stack:
>>>> [ERROR] Failed to execute goal on project
>>>> applicationContextComponents: Could not resolve dependencies for
>>>> project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>> 0
>>>> -
>>>> rc-4-SNAPSHOT: Failure to find
>>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> e s was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced -> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal on project applicationContextComponents: Could not
>>>> resolve dependencies for project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>>> at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>> at
>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>> at
>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>> at
>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>> at
>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>> 3
>>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>>> Could not resolve dependencies for project
>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>> at
>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>>> ... 22 more
>>>> Caused by:
>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>>> at
>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>>> ... 23 more
>>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>>> ... 24 more
>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>>> es was cached in the local repository, resolution will not be
>>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>>> has elapsed or updates are forced
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>>> at
>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(De
>>>> f
>>>> a
>>>> ultArtifactResolver.java:427)
>>>>
>>>> John "Caolan" Dix
>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>>> Division
>>>> o: 206-288-0334 m: 425.351.7340
>>> Why is Maven looking in the "releases" repository on Nexus?
>>>
>>> I would expect it to be looking at either public (if you use the
>>> group), or the mirror of central.
>>>
>>> . . . just my naive two cents.
>>> /mde/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and
>>> confidential and subject to the Amdocs policy statement, you may
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may review
> at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
What I mean by being "downloaded" is that it is easily found in the local .m2 repository of the machine maven is being executed on.
-----Original Message-----
From: John Dix
Sent: Monday, September 09, 2013 9:44 AM
To: Maven Developers List
Subject: RE: Failure to find artifact in Nexus
Thanks!
The problem is not that I am not getting the artifact because I am. The problem is that Maven acts like it doesn't have the file(after downloading it) and then exits. If I rerun the build it passes just fine. It does this on very specific artifacts every time. It is very reproducible. What I am trying to find out is why it is doing this so that I can correct the behaviour.
-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Saturday, September 07, 2013 10:02 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus
hi,
/nexus/content/repositories/releases should be used for releases of your company or project /nexus/content/repositories/thirdparty should be used for ... third party artifacts.
Developers should connect to a repository-*group* instead of a repository-*host*, so the Nexus administrator can control which hosted and proxied repositories should be available for them (on URL to rule them all).
Normally this would be the .../public repository
What I don't understand is what you mean with the file being downloaded.
Maven always comes with 2 lines:
Downloading .... which mean it will *try* to download this file Downloaded .... means that Maven succeeded.
If you don't see the second line, then it is not downloaded.
I guess that confused you a bit.
Robert
Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix <Jo...@amdocs.com>:
> + maven dev team..
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 11:08 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Let me rephrase this. It is finding it in the repository we have it in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> , which is where the artifact ISN'T, maven says "Oops. I can't find it
> I give up" and craps out DESPITE the fact that it has already found it
> and downloaded the file.
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 10:59 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a
> second time it bypasses the error.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, September 05, 2013 6:49 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
>
> Is the artifact
>
> commons-httpclient:commons-httpclient:jar:3.1
>
> in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> repo?
>
> That will split your problem in half.
>
> Ron
>
> On 05/09/2013 8:17 PM, John Dix wrote:
>> Mark: We are going to our own Nexus repository:
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s
>>
>> -----Original Message-----
>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>> Sent: Thursday, September 05, 2013 5:03 PM
>> To: Maven Users List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> On 9/5/2013 4:47 PM, John Dix wrote:
>>> Hello everyone,
>>>
>>> I have hit a wall in trying to figure out why we're getting this
>>> failure:
>>>
>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>>
>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>> ~/.m2/repository/*) and executing the following command:
>>>
>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>> the first time and then after that it picks up the file. It happens
>>> on the SAME file everytime after a wiping of the .ms/repository
>>> directory. I have looked and visually verified that the jar file it
>>> is looking for is in the .m2 repo and is the correct version it is
>>> looking for. I have tried using the -U switch with the maven command
>>> to no avail. We are getting this on one more jar file after this one
>>> gets resolved but it behaves the same: rerun and it finds it. We do
>>> not encounter this on other products, just this one.
>>>
>>> Does anyone have any idea on how to move forward on this? I am at a
>>> loss.
>>>
>>> Regards!
>>> -Caolan.
>>>
>>> Maven essentials:
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>> arch: "amd64", family: "unix"
>>>
>>>
>>> Full Stack:
>>> [ERROR] Failed to execute goal on project
>>> applicationContextComponents: Could not resolve dependencies for
>>> project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>> 0
>>> -
>>> rc-4-SNAPSHOT: Failure to find
>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal on project applicationContextComponents: Could not
>>> resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at
>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at
>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>> 3
>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>> Could not resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>> ... 22 more
>>> Caused by:
>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>> ... 23 more
>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>> ... 24 more
>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(De
>>> f
>>> a
>>> ultArtifactResolver.java:427)
>>>
>>> John "Caolan" Dix
>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>> Division
>>> o: 206-288-0334 m: 425.351.7340
>> Why is Maven looking in the "releases" repository on Nexus?
>>
>> I would expect it to be looking at either public (if you use the
>> group), or the mirror of central.
>>
>> . . . just my naive two cents.
>> /mde/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
Thanks!
The problem is not that I am not getting the artifact because I am. The problem is that Maven acts like it doesn't have the file(after downloading it) and then exits. If I rerun the build it passes just fine. It does this on very specific artifacts every time. It is very reproducible. What I am trying to find out is why it is doing this so that I can correct the behaviour.
-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Saturday, September 07, 2013 10:02 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus
hi,
/nexus/content/repositories/releases should be used for releases of your company or project /nexus/content/repositories/thirdparty should be used for ... third party artifacts.
Developers should connect to a repository-*group* instead of a repository-*host*, so the Nexus administrator can control which hosted and proxied repositories should be available for them (on URL to rule them all).
Normally this would be the .../public repository
What I don't understand is what you mean with the file being downloaded.
Maven always comes with 2 lines:
Downloading .... which mean it will *try* to download this file Downloaded .... means that Maven succeeded.
If you don't see the second line, then it is not downloaded.
I guess that confused you a bit.
Robert
Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix <Jo...@amdocs.com>:
> + maven dev team..
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 11:08 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Let me rephrase this. It is finding it in the repository we have it in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> , which is where the artifact ISN'T, maven says "Oops. I can't find it
> I give up" and craps out DESPITE the fact that it has already found it
> and downloaded the file.
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 10:59 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a
> second time it bypasses the error.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, September 05, 2013 6:49 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
>
> Is the artifact
>
> commons-httpclient:commons-httpclient:jar:3.1
>
> in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> repo?
>
> That will split your problem in half.
>
> Ron
>
> On 05/09/2013 8:17 PM, John Dix wrote:
>> Mark: We are going to our own Nexus repository:
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s
>>
>> -----Original Message-----
>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>> Sent: Thursday, September 05, 2013 5:03 PM
>> To: Maven Users List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> On 9/5/2013 4:47 PM, John Dix wrote:
>>> Hello everyone,
>>>
>>> I have hit a wall in trying to figure out why we're getting this
>>> failure:
>>>
>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>>
>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>> ~/.m2/repository/*) and executing the following command:
>>>
>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>> the first time and then after that it picks up the file. It happens
>>> on the SAME file everytime after a wiping of the .ms/repository
>>> directory. I have looked and visually verified that the jar file it
>>> is looking for is in the .m2 repo and is the correct version it is
>>> looking for. I have tried using the -U switch with the maven command
>>> to no avail. We are getting this on one more jar file after this one
>>> gets resolved but it behaves the same: rerun and it finds it. We do
>>> not encounter this on other products, just this one.
>>>
>>> Does anyone have any idea on how to move forward on this? I am at a
>>> loss.
>>>
>>> Regards!
>>> -Caolan.
>>>
>>> Maven essentials:
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>> arch: "amd64", family: "unix"
>>>
>>>
>>> Full Stack:
>>> [ERROR] Failed to execute goal on project
>>> applicationContextComponents: Could not resolve dependencies for
>>> project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>> 0
>>> -
>>> rc-4-SNAPSHOT: Failure to find
>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal on project applicationContextComponents: Could not
>>> resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at
>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at
>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>> 3
>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>> Could not resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>> ... 22 more
>>> Caused by:
>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>> ... 23 more
>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>> ... 24 more
>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> es was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(De
>>> f
>>> a
>>> ultArtifactResolver.java:427)
>>>
>>> John "Caolan" Dix
>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>> Division
>>> o: 206-288-0334 m: 425.351.7340
>> Why is Maven looking in the "releases" repository on Nexus?
>>
>> I would expect it to be looking at either public (if you use the
>> group), or the mirror of central.
>>
>> . . . just my naive two cents.
>> /mde/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Robert Scholte <rf...@apache.org>.
hi,
/nexus/content/repositories/releases should be used for releases of your
company or project
/nexus/content/repositories/thirdparty should be used for ... third party
artifacts.
Developers should connect to a repository-*group* instead of a
repository-*host*, so the Nexus administrator can control which hosted and
proxied repositories should be available for them (on URL to rule them
all).
Normally this would be the .../public repository
What I don't understand is what you mean with the file being downloaded.
Maven always comes with 2 lines:
Downloading .... which mean it will *try* to download this file
Downloaded .... means that Maven succeeded.
If you don't see the second line, then it is not downloaded.
I guess that confused you a bit.
Robert
Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix <Jo...@amdocs.com>:
> + maven dev team..
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 11:08 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Let me rephrase this. It is finding it in the repository we have it in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases,
> which is where the artifact ISN'T, maven says "Oops. I can't find it I
> give up" and craps out DESPITE the fact that it has already found it and
> downloaded the file.
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 10:59 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a
> second time it bypasses the error.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, September 05, 2013 6:49 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
>
> Is the artifact
>
> commons-httpclient:commons-httpclient:jar:3.1
>
> in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> repo?
>
> That will split your problem in half.
>
> Ron
>
> On 05/09/2013 8:17 PM, John Dix wrote:
>> Mark: We are going to our own Nexus repository:
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>
>> -----Original Message-----
>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>> Sent: Thursday, September 05, 2013 5:03 PM
>> To: Maven Users List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> On 9/5/2013 4:47 PM, John Dix wrote:
>>> Hello everyone,
>>>
>>> I have hit a wall in trying to figure out why we're getting this
>>> failure:
>>>
>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>>
>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>> ~/.m2/repository/*) and executing the following command:
>>>
>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
>>> the first time and then after that it picks up the file. It happens on
>>> the SAME file everytime after a wiping of the .ms/repository
>>> directory. I have looked and visually verified that the jar file it is
>>> looking for is in the .m2 repo and is the correct version it is
>>> looking for. I have tried using the -U switch with the maven command
>>> to no avail. We are getting this on one more jar file after this one
>>> gets resolved but it behaves the same: rerun and it finds it. We do
>>> not encounter this on other products, just this one.
>>>
>>> Does anyone have any idea on how to move forward on this? I am at a
>>> loss.
>>>
>>> Regards!
>>> -Caolan.
>>>
>>> Maven essentials:
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>> arch: "amd64", family: "unix"
>>>
>>>
>>> Full Stack:
>>> [ERROR] Failed to execute goal on project
>>> applicationContextComponents: Could not resolve dependencies for
>>> project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0
>>> -
>>> rc-4-SNAPSHOT: Failure to find
>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal on project applicationContextComponents: Could not
>>> resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>> was cached in the local repository, resolution will not be reattempted
>>> until the update interval of qpass-nexus-hosted-releases has elapsed
>>> or updates are forced
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at
>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at
>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>> 3
>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>> Could not resolve dependencies for project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>> was cached in the local repository, resolution will not be reattempted
>>> until the update interval of qpass-nexus-hosted-releases has elapsed
>>> or updates are forced
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>> ... 22 more
>>> Caused by:
>>> org.sonatype.aether.resolution.DependencyResolutionException: Failure
>>> to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>> was cached in the local repository, resolution will not be reattempted
>>> until the update interval of qpass-nexus-hosted-releases has elapsed
>>> or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>> at
>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>> ... 23 more
>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>> was cached in the local repository, resolution will not be reattempted
>>> until the update interval of qpass-nexus-hosted-releases has elapsed
>>> or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>> ... 24 more
>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>> was cached in the local repository, resolution will not be reattempted
>>> until the update interval of qpass-nexus-hosted-releases has elapsed
>>> or updates are forced
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def
>>> a
>>> ultArtifactResolver.java:427)
>>>
>>> John "Caolan" Dix
>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>> Division
>>> o: 206-288-0334 m: 425.351.7340
>> Why is Maven looking in the "releases" repository on Nexus?
>>
>> I would expect it to be looking at either public (if you use the
>> group), or the mirror of central.
>>
>> . . . just my naive two cents.
>> /mde/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
However, we are using the same settings.xml file for all of our projects, not just the one we are getting the errors on, and they all seem to work.
-----Original Message-----
From: John Dix
Sent: Tuesday, September 10, 2013 9:43 AM
To: Maven Users List
Cc: rwheeler@artifact-software.com
Subject: RE: Failure to find artifact in Nexus
Agreed. It is a hack... I am fairly new to maven and I work on a very complex system I did not design (in fact nobody here is left who did design it). Do you have suggestions on how to approach debugging this problem?
-----Original Message-----
From: Brian Fox [mailto:brianf@infinity.nu]
Sent: Tuesday, September 10, 2013 4:24 AM
To: Maven Users List
Cc: rwheeler@artifact-software.com
Subject: Re: Failure to find artifact in Nexus
You still have something wrong with the repositories in your pom or the settings.xml. Making requests to Nexus ..../releases would generally only be done for _your_ internal components, not for things like http client or the clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven opts fix you refer to above is a hack around that.
On Mon, Sep 9, 2013 at 4:02 PM, John Dix <Jo...@amdocs.com> wrote:
> FYI https://jira.codehaus.org/browse/MNG-5181 ... The use of the
> MAVEN_OPTS flag has resolved this issue for us. However now it is
> telling us that maven-clean-plugin 2.5 cannot be found in our release repository.
> This might be an ancillary issue as we have not encountered this
> before until I used the workaround given in the Jira bug.
>
> It feels more like a hack than a fix as I am basically telling it to
> not be 3.1 and act like 2.x, which kind of defeats the purpose of
> upgrading out of 2.x IMO.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Friday, September 06, 2013 12:59 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
> What is in your settings.xml file?
>
> Do you have anything about repos in your POMs?
>
> Ron
> On 06/09/2013 2:09 PM, John Dix wrote:
> > + maven dev team..
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 11:08 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Let me rephrase this. It is finding it in the repository we have it
> > in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> , which is where the artifact ISN'T, maven says "Oops. I can't find it
> I give up" and craps out DESPITE the fact that it has already found it
> and downloaded the file.
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 10:59 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a
> second time it bypasses the error.
> >
> > -----Original Message-----
> > From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> > Sent: Thursday, September 05, 2013 6:49 PM
> > To: users@maven.apache.org
> > Subject: Re: Failure to find artifact in Nexus
> >
> >
> > Is the artifact
> >
> > commons-httpclient:commons-httpclient:jar:3.1
> >
> > in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
> >
> > That will split your problem in half.
> >
> > Ron
> >
> > On 05/09/2013 8:17 PM, John Dix wrote:
> >> Mark: We are going to our own Nexus repository:
> >> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
> >> se
> >> s
> >>
> >> -----Original Message-----
> >> From: Mark Eggers [mailto:its_toasted@yahoo.com]
> >> Sent: Thursday, September 05, 2013 5:03 PM
> >> To: Maven Users List
> >> Subject: Re: Failure to find artifact in Nexus
> >>
> >> On 9/5/2013 4:47 PM, John Dix wrote:
> >>> Hello everyone,
> >>>
> >>> I have hit a wall in trying to figure out why we're getting this
> failure:
> >>>
> >>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
> >>> find commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
> >>> as e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of
> >>> qpass-nexus-hosted-releases has elapsed or updates are forced
> >>>
> >>> during our builds. On a clean .m2/repository directory(ran rm -rf
> ~/.m2/repository/*) and executing the following command:
> >>>
> >>> mvn -e -DskipTests clean install -f <path to our pom>. This
> >>> happens
> the first time and then after that it picks up the file. It happens on
> the SAME file everytime after a wiping of the .ms/repository
> directory. I have looked and visually verified that the jar file it is
> looking for is in the
> .m2 repo and is the correct version it is looking for. I have tried
> using the -U switch with the maven command to no avail. We are getting
> this on one more jar file after this one gets resolved but it behaves the same:
> rerun and it finds it. We do not encounter this on other products,
> just this one.
> >>>
> >>> Does anyone have any idea on how to move forward on this? I am at
> >>> a
> loss.
> >>>
> >>> Regards!
> >>> -Caolan.
> >>>
> >>> Maven essentials:
> >>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
> >>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
> >>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
> >>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
> >>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
> >>> arch: "amd64", family: "unix"
> >>>
> >>>
> >>> Full Stack:
> >>> [ERROR] Failed to execute goal on project
> >>> applicationContextComponents: Could not resolve dependencies for
> >>> project
> >>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
> >>> 0
> >>> -
> >>> rc-4-SNAPSHOT: Failure to find
> >>> commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
> >>> as e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of
> >>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
> >>> [Help 1]
> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal on project applicationContextComponents: Could not
> resolve dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDep
> endencies(LifecycleDependencyResolver.java:210)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolv
> eProjectDependencies(LifecycleDependencyResolver.java:117)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAre
> Resolved(MojoExecutor.java:258)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:201)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:153)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:145)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t(LifecycleModuleBuilder.java:84)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t(LifecycleModuleBuilder.java:59)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBui
> ld(LifecycleStarter.java:183)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycle
> Starter.java:161)
> >>> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >>> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >>> at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >>> at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >>> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:57)
> >>> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:43)
> >>> at java.lang.reflect.Method.invoke(Method.java:601)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launc
> her.java:290)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java
> :230)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
> ncher.java:409)
> >>> at
> >>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> >>> 3
> >>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
> >>> Could not resolve dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(De
> faultProjectDependenciesResolver.java:189)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDep
> endencies(LifecycleDependencyResolver.java:185)
> >>> ... 22 more
> >>> Caused by:
> org.sonatype.aether.resolution.DependencyResolutionException: Failure
> to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepen
> dencies(DefaultRepositorySystem.java:375)
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(De
> faultProjectDependenciesResolver.java:183)
> >>> ... 23 more
> >>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Defa
> ultArtifactResolver.java:538)
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtif
> acts(DefaultArtifactResolver.java:216)
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepen
> dencies(DefaultRepositorySystem.java:358)
> >>> ... 24 more
> >>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newExcepti
> on(DefaultUpdateCheckManager.java:230)
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtif
> act(DefaultUpdateCheckManager.java:176)
> >>> at
> >>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(
> >>> De
> >>> f
> >>> a
> >>> ultArtifactResolver.java:427)
> >>>
> >>> John "Caolan" Dix
> >>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
> >>> Division
> >>> o: 206-288-0334 m: 425.351.7340
> >> Why is Maven looking in the "releases" repository on Nexus?
> >>
> >> I would expect it to be looking at either public (if you use the
> group), or the mirror of central.
> >>
> >> . . . just my naive two cents.
> >> /mde/
> >>
> >>
> >>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
Agreed. It is a hack... I am fairly new to maven and I work on a very complex system I did not design (in fact nobody here is left who did design it). Do you have suggestions on how to approach debugging this problem?
-----Original Message-----
From: Brian Fox [mailto:brianf@infinity.nu]
Sent: Tuesday, September 10, 2013 4:24 AM
To: Maven Users List
Cc: rwheeler@artifact-software.com
Subject: Re: Failure to find artifact in Nexus
You still have something wrong with the repositories in your pom or the settings.xml. Making requests to Nexus ..../releases would generally only be done for _your_ internal components, not for things like http client or the clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven opts fix you refer to above is a hack around that.
On Mon, Sep 9, 2013 at 4:02 PM, John Dix <Jo...@amdocs.com> wrote:
> FYI https://jira.codehaus.org/browse/MNG-5181 ... The use of the
> MAVEN_OPTS flag has resolved this issue for us. However now it is
> telling us that maven-clean-plugin 2.5 cannot be found in our release repository.
> This might be an ancillary issue as we have not encountered this
> before until I used the workaround given in the Jira bug.
>
> It feels more like a hack than a fix as I am basically telling it to
> not be 3.1 and act like 2.x, which kind of defeats the purpose of
> upgrading out of 2.x IMO.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Friday, September 06, 2013 12:59 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
> What is in your settings.xml file?
>
> Do you have anything about repos in your POMs?
>
> Ron
> On 06/09/2013 2:09 PM, John Dix wrote:
> > + maven dev team..
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 11:08 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Let me rephrase this. It is finding it in the repository we have it
> > in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> , which is where the artifact ISN'T, maven says "Oops. I can't find it
> I give up" and craps out DESPITE the fact that it has already found it
> and downloaded the file.
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 10:59 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a
> second time it bypasses the error.
> >
> > -----Original Message-----
> > From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> > Sent: Thursday, September 05, 2013 6:49 PM
> > To: users@maven.apache.org
> > Subject: Re: Failure to find artifact in Nexus
> >
> >
> > Is the artifact
> >
> > commons-httpclient:commons-httpclient:jar:3.1
> >
> > in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
> >
> > That will split your problem in half.
> >
> > Ron
> >
> > On 05/09/2013 8:17 PM, John Dix wrote:
> >> Mark: We are going to our own Nexus repository:
> >> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
> >> se
> >> s
> >>
> >> -----Original Message-----
> >> From: Mark Eggers [mailto:its_toasted@yahoo.com]
> >> Sent: Thursday, September 05, 2013 5:03 PM
> >> To: Maven Users List
> >> Subject: Re: Failure to find artifact in Nexus
> >>
> >> On 9/5/2013 4:47 PM, John Dix wrote:
> >>> Hello everyone,
> >>>
> >>> I have hit a wall in trying to figure out why we're getting this
> failure:
> >>>
> >>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
> >>> find commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
> >>> as e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of
> >>> qpass-nexus-hosted-releases has elapsed or updates are forced
> >>>
> >>> during our builds. On a clean .m2/repository directory(ran rm -rf
> ~/.m2/repository/*) and executing the following command:
> >>>
> >>> mvn -e -DskipTests clean install -f <path to our pom>. This
> >>> happens
> the first time and then after that it picks up the file. It happens on
> the SAME file everytime after a wiping of the .ms/repository
> directory. I have looked and visually verified that the jar file it is
> looking for is in the
> .m2 repo and is the correct version it is looking for. I have tried
> using the -U switch with the maven command to no avail. We are getting
> this on one more jar file after this one gets resolved but it behaves the same:
> rerun and it finds it. We do not encounter this on other products,
> just this one.
> >>>
> >>> Does anyone have any idea on how to move forward on this? I am at
> >>> a
> loss.
> >>>
> >>> Regards!
> >>> -Caolan.
> >>>
> >>> Maven essentials:
> >>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
> >>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
> >>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
> >>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
> >>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
> >>> arch: "amd64", family: "unix"
> >>>
> >>>
> >>> Full Stack:
> >>> [ERROR] Failed to execute goal on project
> >>> applicationContextComponents: Could not resolve dependencies for
> >>> project
> >>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
> >>> 0
> >>> -
> >>> rc-4-SNAPSHOT: Failure to find
> >>> commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
> >>> as e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of
> >>> qpass-nexus-hosted-releases has elapsed or updates are forced ->
> >>> [Help 1]
> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal on project applicationContextComponents: Could not
> resolve dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDep
> endencies(LifecycleDependencyResolver.java:210)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolv
> eProjectDependencies(LifecycleDependencyResolver.java:117)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAre
> Resolved(MojoExecutor.java:258)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:201)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:153)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:145)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t(LifecycleModuleBuilder.java:84)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t(LifecycleModuleBuilder.java:59)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBui
> ld(LifecycleStarter.java:183)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycle
> Starter.java:161)
> >>> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >>> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >>> at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >>> at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >>> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:57)
> >>> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:43)
> >>> at java.lang.reflect.Method.invoke(Method.java:601)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launc
> her.java:290)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java
> :230)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
> ncher.java:409)
> >>> at
> >>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> >>> 3
> >>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
> >>> Could not resolve dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(De
> faultProjectDependenciesResolver.java:189)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDep
> endencies(LifecycleDependencyResolver.java:185)
> >>> ... 22 more
> >>> Caused by:
> org.sonatype.aether.resolution.DependencyResolutionException: Failure
> to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepen
> dencies(DefaultRepositorySystem.java:375)
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(De
> faultProjectDependenciesResolver.java:183)
> >>> ... 23 more
> >>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Defa
> ultArtifactResolver.java:538)
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtif
> acts(DefaultArtifactResolver.java:216)
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepen
> dencies(DefaultRepositorySystem.java:358)
> >>> ... 24 more
> >>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
> was cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed
> or updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newExcepti
> on(DefaultUpdateCheckManager.java:230)
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtif
> act(DefaultUpdateCheckManager.java:176)
> >>> at
> >>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(
> >>> De
> >>> f
> >>> a
> >>> ultArtifactResolver.java:427)
> >>>
> >>> John "Caolan" Dix
> >>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
> >>> Division
> >>> o: 206-288-0334 m: 425.351.7340
> >> Why is Maven looking in the "releases" repository on Nexus?
> >>
> >> I would expect it to be looking at either public (if you use the
> group), or the mirror of central.
> >>
> >> . . . just my naive two cents.
> >> /mde/
> >>
> >>
> >>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Brian Fox <br...@infinity.nu>.
You still have something wrong with the repositories in your pom or the
settings.xml. Making requests to Nexus ..../releases would generally only
be done for _your_ internal components, not for things like http client or
the clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven
opts fix you refer to above is a hack around that.
On Mon, Sep 9, 2013 at 4:02 PM, John Dix <Jo...@amdocs.com> wrote:
> FYI https://jira.codehaus.org/browse/MNG-5181 ... The use of the
> MAVEN_OPTS flag has resolved this issue for us. However now it is telling
> us that maven-clean-plugin 2.5 cannot be found in our release repository.
> This might be an ancillary issue as we have not encountered this before
> until I used the workaround given in the Jira bug.
>
> It feels more like a hack than a fix as I am basically telling it to not
> be 3.1 and act like 2.x, which kind of defeats the purpose of upgrading out
> of 2.x IMO.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Friday, September 06, 2013 12:59 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
> What is in your settings.xml file?
>
> Do you have anything about repos in your POMs?
>
> Ron
> On 06/09/2013 2:09 PM, John Dix wrote:
> > + maven dev team..
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 11:08 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Let me rephrase this. It is finding it in the repository we have it in
> (3rdparty), but when it gets to
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases,
> which is where the artifact ISN'T, maven says "Oops. I can't find it I give
> up" and craps out DESPITE the fact that it has already found it and
> downloaded the file.
> >
> > -----Original Message-----
> > From: John Dix
> > Sent: Friday, September 06, 2013 10:59 AM
> > To: Maven Users List; rwheeler@artifact-software.com
> > Subject: RE: Failure to find artifact in Nexus
> >
> > Yes it is. It downloads the file. I have verified it is in the .m2
> repository on the drive where the build is located. When I execute a second
> time it bypasses the error.
> >
> > -----Original Message-----
> > From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> > Sent: Thursday, September 05, 2013 6:49 PM
> > To: users@maven.apache.org
> > Subject: Re: Failure to find artifact in Nexus
> >
> >
> > Is the artifact
> >
> > commons-httpclient:commons-httpclient:jar:3.1
> >
> > in the
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
> >
> > That will split your problem in half.
> >
> > Ron
> >
> > On 05/09/2013 8:17 PM, John Dix wrote:
> >> Mark: We are going to our own Nexus repository:
> >> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
> >> s
> >>
> >> -----Original Message-----
> >> From: Mark Eggers [mailto:its_toasted@yahoo.com]
> >> Sent: Thursday, September 05, 2013 5:03 PM
> >> To: Maven Users List
> >> Subject: Re: Failure to find artifact in Nexus
> >>
> >> On 9/5/2013 4:47 PM, John Dix wrote:
> >>> Hello everyone,
> >>>
> >>> I have hit a wall in trying to figure out why we're getting this
> failure:
> >>>
> >>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
> >>> find commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
> >>> e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of qpass-nexus-hosted-releases
> >>> has elapsed or updates are forced
> >>>
> >>> during our builds. On a clean .m2/repository directory(ran rm -rf
> ~/.m2/repository/*) and executing the following command:
> >>>
> >>> mvn -e -DskipTests clean install -f <path to our pom>. This happens
> the first time and then after that it picks up the file. It happens on the
> SAME file everytime after a wiping of the .ms/repository directory. I have
> looked and visually verified that the jar file it is looking for is in the
> .m2 repo and is the correct version it is looking for. I have tried using
> the -U switch with the maven command to no avail. We are getting this on
> one more jar file after this one gets resolved but it behaves the same:
> rerun and it finds it. We do not encounter this on other products, just
> this one.
> >>>
> >>> Does anyone have any idea on how to move forward on this? I am at a
> loss.
> >>>
> >>> Regards!
> >>> -Caolan.
> >>>
> >>> Maven essentials:
> >>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
> >>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
> >>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
> >>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
> >>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
> >>> arch: "amd64", family: "unix"
> >>>
> >>>
> >>> Full Stack:
> >>> [ERROR] Failed to execute goal on project
> >>> applicationContextComponents: Could not resolve dependencies for
> >>> project
> >>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
> >>> 0
> >>> -
> >>> rc-4-SNAPSHOT: Failure to find
> >>> commons-httpclient:commons-httpclient:jar:3.1 in
> >>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
> >>> e s was cached in the local repository, resolution will not be
> >>> reattempted until the update interval of qpass-nexus-hosted-releases
> >>> has elapsed or updates are forced -> [Help 1]
> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal on project applicationContextComponents: Could not resolve
> dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releaseswas cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed or
> updates are forced
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> >>> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >>> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >>> at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >>> at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >>> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>> at java.lang.reflect.Method.invoke(Method.java:601)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >>> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> >>> at
> >>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> >>> 3
> >>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
> >>> Could not resolve dependencies for project
> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releaseswas cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed or
> updates are forced
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
> >>> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
> >>> ... 22 more
> >>> Caused by:
> org.sonatype.aether.resolution.DependencyResolutionException: Failure to
> find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releaseswas cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed or
> updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
> >>> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
> >>> ... 23 more
> >>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releaseswas cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed or
> updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
> >>> at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
> >>> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
> >>> ... 24 more
> >>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in
> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releaseswas cached in the local repository, resolution will not be reattempted
> until the update interval of qpass-nexus-hosted-releases has elapsed or
> updates are forced
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
> >>> at
> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
> >>> at
> >>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(De
> >>> f
> >>> a
> >>> ultArtifactResolver.java:427)
> >>>
> >>> John "Caolan" Dix
> >>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
> >>> Division
> >>> o: 206-288-0334 m: 425.351.7340
> >> Why is Maven looking in the "releases" repository on Nexus?
> >>
> >> I would expect it to be looking at either public (if you use the
> group), or the mirror of central.
> >>
> >> . . . just my naive two cents.
> >> /mde/
> >>
> >>
> >>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Failure to find artifact in Nexus
Posted by John Dix <Jo...@amdocs.com>.
FYI https://jira.codehaus.org/browse/MNG-5181 ... The use of the MAVEN_OPTS flag has resolved this issue for us. However now it is telling us that maven-clean-plugin 2.5 cannot be found in our release repository. This might be an ancillary issue as we have not encountered this before until I used the workaround given in the Jira bug.
It feels more like a hack than a fix as I am basically telling it to not be 3.1 and act like 2.x, which kind of defeats the purpose of upgrading out of 2.x IMO.
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Friday, September 06, 2013 12:59 PM
To: users@maven.apache.org
Subject: Re: Failure to find artifact in Nexus
What is in your settings.xml file?
Do you have anything about repos in your POMs?
Ron
On 06/09/2013 2:09 PM, John Dix wrote:
> + maven dev team..
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 11:08 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Let me rephrase this. It is finding it in the repository we have it in (3rdparty), but when it gets to http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases, which is where the artifact ISN'T, maven says "Oops. I can't find it I give up" and craps out DESPITE the fact that it has already found it and downloaded the file.
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 10:59 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Yes it is. It downloads the file. I have verified it is in the .m2 repository on the drive where the build is located. When I execute a second time it bypasses the error.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, September 05, 2013 6:49 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
>
> Is the artifact
>
> commons-httpclient:commons-httpclient:jar:3.1
>
> in the http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases repo?
>
> That will split your problem in half.
>
> Ron
>
> On 05/09/2013 8:17 PM, John Dix wrote:
>> Mark: We are going to our own Nexus repository:
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>> s
>>
>> -----Original Message-----
>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>> Sent: Thursday, September 05, 2013 5:03 PM
>> To: Maven Users List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> On 9/5/2013 4:47 PM, John Dix wrote:
>>> Hello everyone,
>>>
>>> I have hit a wall in trying to figure out why we're getting this failure:
>>>
>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>>
>>> during our builds. On a clean .m2/repository directory(ran rm -rf ~/.m2/repository/*) and executing the following command:
>>>
>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens the first time and then after that it picks up the file. It happens on the SAME file everytime after a wiping of the .ms/repository directory. I have looked and visually verified that the jar file it is looking for is in the .m2 repo and is the correct version it is looking for. I have tried using the -U switch with the maven command to no avail. We are getting this on one more jar file after this one gets resolved but it behaves the same: rerun and it finds it. We do not encounter this on other products, just this one.
>>>
>>> Does anyone have any idea on how to move forward on this? I am at a loss.
>>>
>>> Regards!
>>> -Caolan.
>>>
>>> Maven essentials:
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>> arch: "amd64", family: "unix"
>>>
>>>
>>> Full Stack:
>>> [ERROR] Failed to execute goal on project
>>> applicationContextComponents: Could not resolve dependencies for
>>> project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>> 0
>>> -
>>> rc-4-SNAPSHOT: Failure to find
>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project applicationContextComponents: Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>> 3
>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>> Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>> ... 22 more
>>> Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>> ... 23 more
>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>> ... 24 more
>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(De
>>> f
>>> a
>>> ultArtifactResolver.java:427)
>>>
>>> John "Caolan" Dix
>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>> Division
>>> o: 206-288-0334 m: 425.351.7340
>> Why is Maven looking in the "releases" repository on Nexus?
>>
>> I would expect it to be looking at either public (if you use the group), or the mirror of central.
>>
>> . . . just my naive two cents.
>> /mde/
>>
>>
>>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failure to find artifact in Nexus
Posted by Ron Wheeler <rw...@artifact-software.com>.
What is in your settings.xml file?
Do you have anything about repos in your POMs?
Ron
On 06/09/2013 2:09 PM, John Dix wrote:
> + maven dev team..
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 11:08 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Let me rephrase this. It is finding it in the repository we have it in (3rdparty), but when it gets to http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases, which is where the artifact ISN'T, maven says "Oops. I can't find it I give up" and craps out DESPITE the fact that it has already found it and downloaded the file.
>
> -----Original Message-----
> From: John Dix
> Sent: Friday, September 06, 2013 10:59 AM
> To: Maven Users List; rwheeler@artifact-software.com
> Subject: RE: Failure to find artifact in Nexus
>
> Yes it is. It downloads the file. I have verified it is in the .m2 repository on the drive where the build is located. When I execute a second time it bypasses the error.
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, September 05, 2013 6:49 PM
> To: users@maven.apache.org
> Subject: Re: Failure to find artifact in Nexus
>
>
> Is the artifact
>
> commons-httpclient:commons-httpclient:jar:3.1
>
> in the http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases repo?
>
> That will split your problem in half.
>
> Ron
>
> On 05/09/2013 8:17 PM, John Dix wrote:
>> Mark: We are going to our own Nexus repository:
>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
>>
>> -----Original Message-----
>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>> Sent: Thursday, September 05, 2013 5:03 PM
>> To: Maven Users List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> On 9/5/2013 4:47 PM, John Dix wrote:
>>> Hello everyone,
>>>
>>> I have hit a wall in trying to figure out why we're getting this failure:
>>>
>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
>>> find commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced
>>>
>>> during our builds. On a clean .m2/repository directory(ran rm -rf ~/.m2/repository/*) and executing the following command:
>>>
>>> mvn -e -DskipTests clean install -f <path to our pom>. This happens the first time and then after that it picks up the file. It happens on the SAME file everytime after a wiping of the .ms/repository directory. I have looked and visually verified that the jar file it is looking for is in the .m2 repo and is the correct version it is looking for. I have tried using the -U switch with the maven command to no avail. We are getting this on one more jar file after this one gets resolved but it behaves the same: rerun and it finds it. We do not encounter this on other products, just this one.
>>>
>>> Does anyone have any idea on how to move forward on this? I am at a loss.
>>>
>>> Regards!
>>> -Caolan.
>>>
>>> Maven essentials:
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>> arch: "amd64", family: "unix"
>>>
>>>
>>> Full Stack:
>>> [ERROR] Failed to execute goal on project
>>> applicationContextComponents: Could not resolve dependencies for
>>> project
>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0
>>> -
>>> rc-4-SNAPSHOT: Failure to find
>>> commons-httpclient:commons-httpclient:jar:3.1 in
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
>>> s was cached in the local repository, resolution will not be
>>> reattempted until the update interval of qpass-nexus-hosted-releases
>>> has elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project applicationContextComponents: Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>> 3
>>> 52) Caused by: org.apache.maven.project.DependencyResolutionException:
>>> Could not resolve dependencies for project com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0-rc-4-SNAPSHOT: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
>>> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
>>> ... 22 more
>>> Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
>>> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
>>> ... 23 more
>>> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
>>> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
>>> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
>>> ... 24 more
>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find commons-httpclient:commons-httpclient:jar:3.1 in http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases was cached in the local repository, resolution will not be reattempted until the update interval of qpass-nexus-hosted-releases has elapsed or updates are forced
>>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
>>> at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:176)
>>> at
>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def
>>> a
>>> ultArtifactResolver.java:427)
>>>
>>> John "Caolan" Dix
>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services
>>> Division
>>> o: 206-288-0334 m: 425.351.7340
>> Why is Maven looking in the "releases" repository on Nexus?
>>
>> I would expect it to be looking at either public (if you use the group), or the mirror of central.
>>
>> . . . just my naive two cents.
>> /mde/
>>
>>
>>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org