RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
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"
>>>
>>>
>>> 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.ma

Configurable behavior on empty assemblies

2013-09-09 Thread Jeffrey E Care
I'm packaging my (multi-module) product using an assembly of assemblies 
approach for projects that have "extra" stuff that needs to be included in 
the distribution (i.e. other than their regular attached JAR). I'm having 
problems with inheriting the assembly plugin executions in cases where 
there is nothing else to package. I can't figure out how to make the 
assembly plugin no-op in cases where it discovers that there is nothing to 
assemble.

Is there such a feature? If not what is the correct way to go about 
requesting it?


Jeffrey E. (Jeff) Care
Advisory Software Engineer | IBM Watson Solutions Release Engineering
email: ca...@us.ibm.com | External: 919-543-4907 | Tie line: 441-4907