Pardon me for not responding. But your reply here is ample explanation for why I did not reply.
The "attitude" I detect from this reply is that explanation. Is "bogus" some new software engineering term I am not familiar with, or just the language used by someone dabbling in software because it's "cool". If it's the later please reserve your reply for another forum. Now, please tell me how version 3.0.5 is the latest release when there is a 3.1.1? If you can't get this right, how I am supposed to take your reply seriously? Just this kind of thing is what aggravates me about the open source approach to software development, particularly getting help with it!!! Mike Michael Tarullo Contractor (Engility Corp) Enterprise Architect NSRR System Administrator FAA WJH Technical Center (609)485-5294 -----Original Message----- From: Jörg Schaible [mailto:joerg.schai...@swisspost.com] Sent: Monday, October 05, 2015 12:08 PM To: users@maven.apache.org Subject: Re: Copy-dependencies goal error You asked the same question before and I gave you the advice to either try latest Maven version or 3.0.5, because 3.1.1. is bogus. You never answered. 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
