Wayne, Thanks for the reply. I forgot to mention in my original post that CURRENTLY I'm using Maven v3.1.1.
But your question is a good one, and something I didn't even consider and therefore try to test. I should be able to revert back to and older version of Maven provided 1) I know what version to revert to (most of the people that devised this process over 5 years ago are not around) and 2) the older version is still available (this originated about 5 years ago)!!! I'll reply back to my original post when/if I find something. 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
