Wayne, I have determined, to the best of my ability, that the version of Maven used to execute this POM was probably about 2.2.1. It could have been an earlier version but not a later.
Now I was able to obtain this version from the Maven archives but one question I have is what POM model version was in effect back then? The current version is 4.0.0. I suspect it was not this. How could I find out? Another problem I'm having with this is even if I do get it to run with this version, it really is not a option to use this version going forward, and I'm not sure how the process running under this version is indicative of a problem with Nexus. So before I even try this, I going to try a more current release of Maven first, and also an older version, but not this much older!!! Mike Michael Tarullo Contractor (Engility Corp) Enterprise Architect NSRR System Administrator FAA WJH Technical Center (609)485-5294 -----Original Message----- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Monday, October 05, 2015 11:16 AM To: Maven Users List Subject: Re: Copy-dependencies goal error Looking at the error message again, I agree there seems to be an issue with this dependency: Failed to read artifact descriptor for org.jvnet.staxex:stax-ex:jar:RELEASE: Failed to resolve version for org.jvnet.staxex:stax-ex:jar:RELEASE: Could not find metadata org.jvnet.staxex:stax-ex/maven-metadata.xml in local (C:\Users\Michael CTR Tarullo.FAA\.m2\super-pom-test-repository-62) I would spend some effort looking into that artifact and sorting out why there seems to be no pom file for it, then most likely you can move forward with the rest. Wayne On Mon, Oct 5, 2015 at 9:34 AM, <michael.ctr.taru...@faa.gov> wrote: > Wayne, > > A few questions before I begin to investigates as per your recommendation. > > Are you a committer or just a user? > > I understand your request to try an older release (and I have every intention > of doing just that) but I'm a bit skeptical. Here's why. This is simply a > file copy operation that works fine on other Fuse components (i.e. ActiveMQ > and CXF). Why would a copy operation (i.e. goal) behave any differently > simply because the files it is copying are different? > > That's what I'm struggling with right now!!! > > Thanks, > Mike > > Michael Tarullo > Contractor (Engility Corp) > Enterprise Architect > NSRR System Administrator > FAA WJH Technical Center > (609)485-5294 > > > -----Original Message----- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: Sunday, October 04, 2015 5:03 PM > To: Maven Users List > Subject: Re: Copy-dependencies goal error > > What version of Maven was this process originally built to run against? > > Can you roll (Maven) back to that version and try again, to confirm it still > works as it did originally? If it does not work, then you know it is not > Maven but rather another tool in the mix like Nexus etc. > > Wayne > > On Fri, Oct 2, 2015 at 1:18 PM, <michael.ctr.taru...@faa.gov> wrote: >> I am currently responsible for a "legacy" POM that copies ZIP files >> >> from the Red Hat JBoss Fuse distro in our Nexus repository manager >> >> to a location on a local worstation. Several ZIP files are copied >> >> from each of the following Fuse components, ActiveMQ, Camel and CXF. >> >> >> >> To perform the copy operation the legacy POM is using the Maven >> >> copy-dependencies goal or the maven-dependency-plugin. >> >> >> >> When this project is executed by Maven for just the ActiveMQ and >> >> CXF Fuse components the designated files are copied fine. When, >> >> however we execute the project to copy the Camel files, the process >> >> fails. >> >> >> >> The directory for the failing artifacts is present in our Nexus >> >> repository manager, and is populated with several artifacts. >> >> >> >> What I do not understand is why Maven is even looking for these >> >> artifacts for a simple copy operation? It appears to me that the >> >> artifacts causing the problem have nothing to do with the copy goal! >> >> >> >> I have posted this problem with Red Hat, who originally helpd our >> >> previous personnel develop this POM. They believe, and I tend to >> >> agree 100%, that this is a Maven problem. >> >> >> >> I have attached our settings.xml, pom.xml and the text of the error >> >> message. >> >> >> >> Can someone please explain why this is happening and how to fix it? >> >> >> >> Thanks, >> >> Mike >> >> >> >> Michael Tarullo >> >> Contractor (Engility Corp) >> >> Enterprise Architect >> >> NSRR System Administrator >> >> FAA WJH Technical Center >> >> (609)485-5294 >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
