RE: Failure to find artifact in Nexus
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: rwhee...@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:bri...@infinity.nu] Sent: Tuesday, September 10, 2013 4:24 AM To: Maven Users List Cc: rwhee...@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 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:rwhee...@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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 > >>>
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:bri...@infinity.nu] Sent: Tuesday, September 10, 2013 4:24 AM To: Maven Users List Cc: rwhee...@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 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:rwhee...@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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 inst
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 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:rwhee...@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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 . 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
RE: Failure to find artifact in Nexus
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:rwhee...@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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 . 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+) 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"
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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 . 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+) 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.ensure
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:rwhee...@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_toas...@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 . 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+) 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) >>
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; rwhee...@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; rwhee...@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:rwhee...@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_toas...@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 . 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+) 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 rea
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; rwhee...@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:rwhee...@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_toas...@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 . 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+) 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.getDependencie
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_toas...@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/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 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 . 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+) 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/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 -> [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.NativeMethodAccessor
RE: Failure to find artifact in Nexus
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_toas...@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/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 > > 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 . 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+) 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/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 -> [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.
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/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 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 . 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+) 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/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 -> [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
Failure to find artifact in Nexus
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/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 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 . 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+) 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/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 -> [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.launche
