You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mi...@faa.gov on 2015/10/02 20:18:42 UTC
Copy-dependencies goal error
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
RE: Copy-dependencies goal error
Posted by Martin Gainty <mg...@hotmail.com>.
Michael-
out of curiosity which stax-ex versions are located at
C:\Users\Michael CTR Tarullo.FAA\.m2\super-pom-test-repository-62\org\jvnet\staxex\stax-ex
concerning version <camel.version>2.15.1.redhat-620133</camel.version>
if you want to implement a specific "version rule" then you'll need to implement
a version rule in <rulesUri>rule-set.xml</rulesUri>
for artifactId versions-maven-plugin plugin
http://www.mojohaus.org/versions-maven-plugin/version-rules.html
hth,
Martin
______________________________________________
From: Michael.CTR.Tarullo@faa.gov
To: users@maven.apache.org
Subject: Copy-dependencies goal error
Date: Fri, 2 Oct 2015 18:18:42 +0000
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
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:waynefay@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, <Mi...@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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Wayne Fay <wa...@gmail.com>.
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, <Mi...@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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Greg,
Thank you for your reply. It is unfortunate that it had to come to this to get an explanation. Why wasn't an explanation like this offered from the beginning? I'm not saying I agree or even like the explanation, but it is an explanation.
I have done some homework on Maven. I would never attempt to use the product without doing so. But if I may speak freely, this product appears to require a certain amount of "esoteric" knowledge. All I want to do is support the task I've been given. Of course I want to know how to use the tool. In fact when I wasn't finding the information I needed to do that, I turned to the Maven User Mailing List. How much knowledge must one have before they do this?
Now let’s look at this particular situation, because I think it just might be unique (but I could be wrong).
In this particular case I inherited a POM file that was developed by people no longer responsible for its upkeep. Those people were assisted by a software vendor that essentially no longer exists, so their employees that helped our people responsible for this are also no longer available either. We have all been in this situation before.
Now the most important thing about this POM is that it is not even building software. You (and a few other people) mention that does not matter. I have a great difference of opinion here. Maven is ostensibly a build tool. Look at its terminology(e.g. as pertains to lifecycle stages). But I think the problem that exists is that in making the product flexible in how it implements its features it has opened the door to be used for more than just building software. I think that is the case here. The original creators of the POM in question used Maven to simply copy some files from one location probably simply because they could. Now I don't know if that was a good or bad idea, all I know is that I have to support it, it broke on my watch and I have to fix it. When I could not figure out how to do that I turned to the Maven community for help, and this is the result of that.
So when you explain to me about dependencies, I understand them in the context of building software, because that's how Maven is supposed to be used. It appears to me that the people that originally developed this POM did not appreciate this when they used it almost as a script to copy files. Now I don't know if that is their fault or Mavens fault, but the simple fact of the matter is that I have to support it. And I would expect more than the struggle I've received during this experience.
I know my attitude has not be the best, but that is what frustration leads to. And certainly the attitude of some of the people you say were trying to "help" should also be addressed here as well.
Sincerely,
Mike
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Greg Trasuk [mailto:trasukg@stratuscom.com]
Sent: Tuesday, October 06, 2015 12:39 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Hi Michael:
Aside - Are you at the FAA tech center in Atlantic City? I taught a course there four days after 9/11. Very nice people there, although the mood wasn’t great at the time, obviously. I particularly enjoyed seeing what I thought was a museum of ancient computers in the cafeteria (core memory and all)- until they explained they were samples of the then-deployed ATC hardware!
Anyhow, I understand your frustration - Maven can have a somewhat steep learning curve. It seems to me that the answers you’ve gotten so far are correct, but perhaps they seem unhelpful because you don’t already have enough knowledge of the product. Unfortunately, with open source, you, the user, need to meet the user list half-way, and get some background knowledge so you can ask the right questions and use the answers effectively. There’s a classic treatise by Eric Raymond on asking questions (http://catb.org/~esr/faqs/smart-questions.html) that you might want to read, although you might not like the content. In fairness, there’s also a newer guide to answering questions out there (https://skippy.net/how-to-answer-questions) that we ought to read every now and then.
In short, you might not like the choice of open source, but I’m guessing your employer already made that choice, and they had good reasons, so… let’s work together!
Let’s start with…
> It is simply copying ZIP/MD5/SHA1 files from a Nexus repository to a local workstation.
You’re mistaken. Maven is not copying files, it is copying dependencies or artifacts. Sorry if this seems like “maven-speak” to you, but you are going to continue to be frustrated until you try to get a clear mental model of what Maven is doing. Let me try to help…
Maven is specifically geared to avoid worrying about where files are on disk. It does this so that (believe it or not) life is easier for developers, since you don’t need to manually manage a library of files that your software might depend on.
So, when you say that you have a POM that “copies files from your nexus repository to a local file system”, that’s not exactly correct, that’s only what it looks like from the outside. In reality, what Maven is doing is attempting to track down all the artifacts that will be needed to fulfull the dependencies that are called out in your POM. Normally, Maven uses all these artifacts as the compile-time class path for compiling other source code to create new artifacts, but in your case, your POM file calls out a build plugin that simply copies all those artifacts to a folder on the local file system.
The idea of an “artifact” is key to understanding Maven. An artifact is typically a jar, war, or ear file that we use, either as a dependency for another artifact, or to install in a server environment. In order to get us away from depending on the file system, an artifact in Maven is identified by its “Maven Coordinates” or “GAV Coordinates”, which are the group id, artifact id, and version of the artifact. The artifact (every artifact!) is described using a POM file. “POM” is unfortunately a bit of a misnomer - it originally means “Project Object Model”, but should really be something like “Artifact Descriptor”, as it’s really associated with the artifact, not a project. Think of the POM as metadata that describes the artifact.
The general idea is that given an artifact’s GAV coordinates, Maven can go off to a repository like Maven Central or your local Nexus repository and retrieve (a) the artifact and (b) the artifact’s metadata, or POM file.
One mistake people make is thinking that the POM file tells Maven what to do. That isn’t correct - the POM file defines what an artifact _is_, and then Maven figures out how to build it, given the packaging type and the set of dependencies that are called out in the POM file. It’s also possible for a POM file to define metadata only, without an actual artifact being specified (otherwise known as a POM artifact, since it calls out ‘pom’ packaging). In this case, we still have GAV coordinates, but they’re more of a metadata identifier. The POM you posted defines a POM artifact with the GAV coordinates “com.iona.fuse:all-products-1.0.0.0-fuse”, and calls out a number of dependencies on activemq, camel, and cxf artifacts.
Generally, “figuring out how to build it” requires Maven to track down and include transitive dependencies. So if I call out Spring Framework version 3.1, maybe it requires Apache commons collections version 2.2. Maven knows that my artifact won’t work without Spring’s dependencies, so it looks up the metadata (POM file) for Spring 3.1, and adds its dependencies (i.e. transient dependencies) to the list of dependencies for my artifact. Maven looks up the dependencies by going out to its repository (i.e. Maven Central or your local Nexus) and asking for the POM files for each of the dependencies. It adds in the transitive dependencies, and then looks up the metadata for those dependencies, and so on, and so on. This is what people mean by “resolving dependencies”.
In your case, your POM file is a little funny - rather than defining an artifact to build, it really exists only to define a set of dependencies and then call out the build plugin called "maven-dependency-plugin”, which is configured to copy the dependencies to the local file system.
Here’s your key point - Maven resolves the dependencies even if your particular plugin configuration is not going to use them - the core maven package doesn’t care about the plugin configuration; it just does its thing, which is resolve dependencies. So even though your plugin configuration specifies “<excludeTransitive>true</excludeTransitive>”, Maven still goes to your Nexus repo and tries to track down those transitive dependencies.
Your error message,
[ERROR] Failed to execute goal on project all-products:
Could not resolve dependencies for project com.iona.fuse:all-products:pom:1.0.0.0-fuse:
Failed to collect dependencies
at org.apache.camel:apache-camel:zip:src:2.15.1.redhat-620133
-> org.apache.camel:camel-cmis:jar:2.15.1.redhat-620133
-> org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.8.0
-> org.apache.chemistry.opencmis:chemistry-opencmis-commons-impl:jar:0.8.0
-> com.sun.xml.ws:jaxws-rt:jar:2.1.7
-> com.sun.xml.stream.buffer:streambuffer:jar:0.9
-> org.jvnet.staxex:stax-ex:jar:RELEASE:
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)
means that when Maven tried to resolve the dependencies for "org.apache.camel:apache-camel:zip:src:2.15.1”, the metadata for that artifact (which is in your repository) included a dependency on "org.jvnet.staxex:stax-ex”, but that artifact is not present in your repository.
The short answer is that you need to get "org.jvnet.staxex:stax-ex” into your repository. It appears to be in Maven Central, so I’m guessing that your Nexus is configured not to act as a proxy to Maven Central. So you’ll need to either load it manually (or use “procurement”) or configure your Nexus to proxy Maven Central (unless of course you can’t do that for security or other reasons, which is why you’d go through procurement).
Since you don’t actually care about the “stax-ex” dependency, you could theoretically load a “dummy” jar and pom that would satisfy the dependency, but that’s really bad practice - some other build might need the real dependency at a later time, so you’re best to get the right files into your repository.
Hope this helps. Also, there’s a webinar I did for my employer that you might enjoy, Maven for Late Adopters (http://www.webagesolutions.com/webinars/registration.html?ApacheMavenLateAdopters). We also offer training and consulting.
Cheers,
Greg Trasuk
> On Oct 5, 2015, at 5:02 PM, <Mi...@faa.gov> <Mi...@faa.gov> wrote:
>
> There are no transitive dependencies!
>
> This is not even building source code!!!
>
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 4:37 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
>> What do you mean by a consistent repository and POM model?
>>
>> If you mean that the POM must be declaring files to copy that are in
>> the repository, that is stating the obvious.
>>
>> And in this case, the POM is doing exactly that. The files I am
>> asking to be copied from the repository are actually in the
>> repository. The problem is that I am getting errors for files I did not ask to be copied.
>
> The repository must also contain all POMs for the transitive dependencies ... otherwise Maven cannot build the project model. Maven core does not know that you have bound an instance of the assembly plugin, that is not interested in the transitive dependencies.
>
>> Did you look at the POM file I attached and compare it to the error
>> messages also attached?
>
> The POMs of the referred artifacts get interesting.
>
> Chrres,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Greg Trasuk <tr...@stratuscom.com>.
Hi Michael:
Aside - Are you at the FAA tech center in Atlantic City? I taught a course there four days after 9/11. Very nice people there, although the mood wasn’t great at the time, obviously. I particularly enjoyed seeing what I thought was a museum of ancient computers in the cafeteria (core memory and all)- until they explained they were samples of the then-deployed ATC hardware!
Anyhow, I understand your frustration - Maven can have a somewhat steep learning curve. It seems to me that the answers you’ve gotten so far are correct, but perhaps they seem unhelpful because you don’t already have enough knowledge of the product. Unfortunately, with open source, you, the user, need to meet the user list half-way, and get some background knowledge so you can ask the right questions and use the answers effectively. There’s a classic treatise by Eric Raymond on asking questions (http://catb.org/~esr/faqs/smart-questions.html) that you might want to read, although you might not like the content. In fairness, there’s also a newer guide to answering questions out there (https://skippy.net/how-to-answer-questions) that we ought to read every now and then.
In short, you might not like the choice of open source, but I’m guessing your employer already made that choice, and they had good reasons, so… let’s work together!
Let’s start with…
> It is simply copying ZIP/MD5/SHA1 files from a Nexus repository to a local workstation.
You’re mistaken. Maven is not copying files, it is copying dependencies or artifacts. Sorry if this seems like “maven-speak” to you, but you are going to continue to be frustrated until you try to get a clear mental model of what Maven is doing. Let me try to help…
Maven is specifically geared to avoid worrying about where files are on disk. It does this so that (believe it or not) life is easier for developers, since you don’t need to manually manage a library of files that your software might depend on.
So, when you say that you have a POM that “copies files from your nexus repository to a local file system”, that’s not exactly correct, that’s only what it looks like from the outside. In reality, what Maven is doing is attempting to track down all the artifacts that will be needed to fulfull the dependencies that are called out in your POM. Normally, Maven uses all these artifacts as the compile-time class path for compiling other source code to create new artifacts, but in your case, your POM file calls out a build plugin that simply copies all those artifacts to a folder on the local file system.
The idea of an “artifact” is key to understanding Maven. An artifact is typically a jar, war, or ear file that we use, either as a dependency for another artifact, or to install in a server environment. In order to get us away from depending on the file system, an artifact in Maven is identified by its “Maven Coordinates” or “GAV Coordinates”, which are the group id, artifact id, and version of the artifact. The artifact (every artifact!) is described using a POM file. “POM” is unfortunately a bit of a misnomer - it originally means “Project Object Model”, but should really be something like “Artifact Descriptor”, as it’s really associated with the artifact, not a project. Think of the POM as metadata that describes the artifact.
The general idea is that given an artifact’s GAV coordinates, Maven can go off to a repository like Maven Central or your local Nexus repository and retrieve (a) the artifact and (b) the artifact’s metadata, or POM file.
One mistake people make is thinking that the POM file tells Maven what to do. That isn’t correct - the POM file defines what an artifact _is_, and then Maven figures out how to build it, given the packaging type and the set of dependencies that are called out in the POM file. It’s also possible for a POM file to define metadata only, without an actual artifact being specified (otherwise known as a POM artifact, since it calls out ‘pom’ packaging). In this case, we still have GAV coordinates, but they’re more of a metadata identifier. The POM you posted defines a POM artifact with the GAV coordinates “com.iona.fuse:all-products-1.0.0.0-fuse”, and calls out a number of dependencies on activemq, camel, and cxf artifacts.
Generally, “figuring out how to build it” requires Maven to track down and include transitive dependencies. So if I call out Spring Framework version 3.1, maybe it requires Apache commons collections version 2.2. Maven knows that my artifact won’t work without Spring’s dependencies, so it looks up the metadata (POM file) for Spring 3.1, and adds its dependencies (i.e. transient dependencies) to the list of dependencies for my artifact. Maven looks up the dependencies by going out to its repository (i.e. Maven Central or your local Nexus) and asking for the POM files for each of the dependencies. It adds in the transitive dependencies, and then looks up the metadata for those dependencies, and so on, and so on. This is what people mean by “resolving dependencies”.
In your case, your POM file is a little funny - rather than defining an artifact to build, it really exists only to define a set of dependencies and then call out the build plugin called "maven-dependency-plugin”, which is configured to copy the dependencies to the local file system.
Here’s your key point - Maven resolves the dependencies even if your particular plugin configuration is not going to use them - the core maven package doesn’t care about the plugin configuration; it just does its thing, which is resolve dependencies. So even though your plugin configuration specifies “<excludeTransitive>true</excludeTransitive>”, Maven still goes to your Nexus repo and tries to track down those transitive dependencies.
Your error message,
[ERROR] Failed to execute goal on project all-products:
Could not resolve dependencies for project com.iona.fuse:all-products:pom:1.0.0.0-fuse:
Failed to collect dependencies
at org.apache.camel:apache-camel:zip:src:2.15.1.redhat-620133
-> org.apache.camel:camel-cmis:jar:2.15.1.redhat-620133
-> org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.8.0
-> org.apache.chemistry.opencmis:chemistry-opencmis-commons-impl:jar:0.8.0
-> com.sun.xml.ws:jaxws-rt:jar:2.1.7
-> com.sun.xml.stream.buffer:streambuffer:jar:0.9
-> org.jvnet.staxex:stax-ex:jar:RELEASE:
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)
means that when Maven tried to resolve the dependencies for "org.apache.camel:apache-camel:zip:src:2.15.1”, the metadata for that artifact (which is in your repository) included a dependency on "org.jvnet.staxex:stax-ex”, but that artifact is not present in your repository.
The short answer is that you need to get "org.jvnet.staxex:stax-ex” into your repository. It appears to be in Maven Central, so I’m guessing that your Nexus is configured not to act as a proxy to Maven Central. So you’ll need to either load it manually (or use “procurement”) or configure your Nexus to proxy Maven Central (unless of course you can’t do that for security or other reasons, which is why you’d go through procurement).
Since you don’t actually care about the “stax-ex” dependency, you could theoretically load a “dummy” jar and pom that would satisfy the dependency, but that’s really bad practice - some other build might need the real dependency at a later time, so you’re best to get the right files into your repository.
Hope this helps. Also, there’s a webinar I did for my employer that you might enjoy, Maven for Late Adopters (http://www.webagesolutions.com/webinars/registration.html?ApacheMavenLateAdopters). We also offer training and consulting.
Cheers,
Greg Trasuk
> On Oct 5, 2015, at 5:02 PM, <Mi...@faa.gov> <Mi...@faa.gov> wrote:
>
> There are no transitive dependencies!
>
> This is not even building source code!!!
>
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 4:37 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
>> What do you mean by a consistent repository and POM model?
>>
>> If you mean that the POM must be declaring files to copy that are in
>> the repository, that is stating the obvious.
>>
>> And in this case, the POM is doing exactly that. The files I am
>> asking to be copied from the repository are actually in the
>> repository. The problem is that I am getting errors for files I did not ask to be copied.
>
> The repository must also contain all POMs for the transitive dependencies ... otherwise Maven cannot build the project model. Maven core does not know that you have bound an instance of the assembly plugin, that is not interested in the transitive dependencies.
>
>> Did you look at the POM file I attached and compare it to the error
>> messages also attached?
>
> The POMs of the referred artifacts get interesting.
>
> Chrres,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@gmx.de>.
Michael.CTR.Tarullo@faa.gov wrote:
> There are no transitive dependencies!
That depends totally on the declaration of the POMs for your dependencies.
You don't control this.
> This is not even building source code!!!
That's totally irrelevant.
> It is simply copying ZIP/MD5/SHA1 files from a Nexus repository to a local
> workstation.
And their POMs which may (and obviously do) declare dependencies again.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
There are no transitive dependencies!
This is not even building source code!!!
It is simply copying ZIP/MD5/SHA1 files from a Nexus repository to a local workstation.
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.schaible@gmx.de]
Sent: Monday, October 05, 2015 4:37 PM
To: users@maven.apache.org
Subject: RE: Copy-dependencies goal error
Hi Michael,
Michael.CTR.Tarullo@faa.gov wrote:
> What do you mean by a consistent repository and POM model?
>
> If you mean that the POM must be declaring files to copy that are in
> the repository, that is stating the obvious.
>
> And in this case, the POM is doing exactly that. The files I am
> asking to be copied from the repository are actually in the
> repository. The problem is that I am getting errors for files I did not ask to be copied.
The repository must also contain all POMs for the transitive dependencies ... otherwise Maven cannot build the project model. Maven core does not know that you have bound an instance of the assembly plugin, that is not interested in the transitive dependencies.
> Did you look at the POM file I attached and compare it to the error
> messages also attached?
The POMs of the referred artifacts get interesting.
Chrres,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Michael,
Michael.CTR.Tarullo@faa.gov wrote:
> What do you mean by a consistent repository and POM model?
>
> If you mean that the POM must be declaring files to copy that are in the
> repository, that is stating the obvious.
>
> And in this case, the POM is doing exactly that. The files I am asking to
> be copied from the repository are actually in the repository. The problem
> is that I am getting errors for files I did not ask to be copied.
The repository must also contain all POMs for the transitive dependencies
... otherwise Maven cannot build the project model. Maven core does not know
that you have bound an instance of the assembly plugin, that is not
interested in the transitive dependencies.
> Did you look at the POM file I attached and compare it to the error
> messages also attached?
The POMs of the referred artifacts get interesting.
Chrres,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Thank you for stating that publicly Karl.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
Sent: Tuesday, October 06, 2015 9:55 AM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Hi Michael,
>
> With all due respect I insulted no one. Am I frustrated? Yes, but I did not insult anyone.
>
> Now I was perfectly fine with letting this go until I received your comment.
> So let me use this opportunity to make a few more comments.
>
> Thank you for suggesting That I go somewhere else for help.
> However, this is the Maven mailing list set up for the express > purpose of getting help with this software.
it is absolutely intended to ask here and I'm your opinion, cause this is User Mailing list...
> Where else do you suggest I go?
Very good question...Unfortunately i haven't got a idea to suggest...
>
> As for the volunteer service you provide, I thank you for that service.
> But when I am dissatisfied with the service I am getting, > please don't throw in my face that you are a volunteer.
> You made that choice.
> And as a result, putting up with frustrated customers
> is something you are going to have to deal with.
> It's part of the deal you signed on to when you volunteered.
> If you are not willing to do that,
> then maybe you should consider not volunteering.
Yes exactly the point.
If those who ansered here and don't like to answer or if they are the opinion to waste their time..than really keep quiet..and let others do the job...
>
> Now I was told by a responder on this thread that I
> am not a customer because I did not pay for this software.
> Nothing could be further from the truth.
There is no one paying for Maven it self...
> In my career I had many "customers" that did not pay for
> the software I was supporting.
> It was my job to provide them the best support that I could.
> I suggest that responders to requests for help on this
> mailing list adopt the same approach, volunteer or not.
Yes...true...
>
> Another responder to this thread brought up that
> he was volunteering and I was wasting his time.
If the original poster is wasting his/here time than just simply don't
do it anymore...
> How about the time of mine he wasted when he suggested
> I try something that made no difference in the outcome,
> and had nothing to do with the problem?
> And this has happened to me before with other
> responders on this mailing list.
>I was in fact told by another responder that the reply of a specific
person
> was off topic and is often the case for that person.
>
> Maybe you should spend some time pointing that out to those individuals
> rather than chastising someone who is simply trying to get help.
>
> Regards,
> Mike
I'm really sorry Michael to read such things in the user mailing list
which is intended for people using Maven and searching for help and
usage of Maven.
To be honest if someone on the user list is the opinion to waste
here/his time just simple keep quiet...or better unsubscribe from the
list...
Maven is an open source project which lives from its community...and
unfortunately i have to say that is not a good attitude of a "community"
against a user....who searches for help...
I never thought i need to write something like this....
Kind regards
Karl Heinz Marbaise
Apache Maven PMC Member
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Helle karl Heinz - thanks for Not considering the OPs Attitude and Tone towards perfectly Fine answers :-/
Bernd
> Am 06.10.2015 um 15:55 schrieb Karl Heinz Marbaise <kh...@gmx.de>:
>
> Hi Michael,
>
> >
>> With all due respect I insulted no one. Am I frustrated? Yes, but I did not insult anyone.
>>
>> Now I was perfectly fine with letting this go until I received your comment.
> > So let me use this opportunity to make a few more comments.
>>
>> Thank you for suggesting That I go somewhere else for help.
> > However, this is the Maven mailing list set up for the express
> > purpose of getting help with this software.
>
> it is absolutely intended to ask here and I'm your opinion, cause this is User Mailing list...
>
>> Where else do you suggest I go?
>
> Very good question...Unfortunately i haven't got a idea to suggest...
>
>
>>
>> As for the volunteer service you provide, I thank you for that service.
> > But when I am dissatisfied with the service I am getting,
> > please don't throw in my face that you are a volunteer.
> > You made that choice.
> > And as a result, putting up with frustrated customers
> > is something you are going to have to deal with.
> > It's part of the deal you signed on to when you volunteered.
> > If you are not willing to do that,
> > then maybe you should consider not volunteering.
>
> Yes exactly the point.
>
> If those who ansered here and don't like to answer or if they are the opinion to waste their time..than really keep quiet..and let others do the job...
>
>>
>> Now I was told by a responder on this thread that I
> > am not a customer because I did not pay for this software.
> > Nothing could be further from the truth.
>
> There is no one paying for Maven it self...
>
> > In my career I had many "customers" that did not pay for
> > the software I was supporting.
> > It was my job to provide them the best support that I could.
>
> > I suggest that responders to requests for help on this
> > mailing list adopt the same approach, volunteer or not.
>
> Yes...true...
>
>>
>> Another responder to this thread brought up that
> > he was volunteering and I was wasting his time.
>
> If the original poster is wasting his/here time than just simply don't do it anymore...
>
>
> > How about the time of mine he wasted when he suggested
> > I try something that made no difference in the outcome,
> > and had nothing to do with the problem?
> > And this has happened to me before with other
> > responders on this mailing list.
>
> >I was in fact told by another responder that the reply of a specific person
> > was off topic and is often the case for that person.
>>
>> Maybe you should spend some time pointing that out to those individuals
> > rather than chastising someone who is simply trying to get help.
>>
>> Regards,
>> Mike
>
> I'm really sorry Michael to read such things in the user mailing list which is intended for people using Maven and searching for help and usage of Maven.
>
>
> To be honest if someone on the user list is the opinion to waste here/his time just simple keep quiet...or better unsubscribe from the list...
>
> Maven is an open source project which lives from its community...and unfortunately i have to say that is not a good attitude of a "community" against a user....who searches for help...
>
> I never thought i need to write something like this....
>
>
> Kind regards
> Karl Heinz Marbaise
> Apache Maven PMC Member
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Michael,
>
> With all due respect I insulted no one. Am I frustrated? Yes, but I did not insult anyone.
>
> Now I was perfectly fine with letting this go until I received your comment.
> So let me use this opportunity to make a few more comments.
>
> Thank you for suggesting That I go somewhere else for help.
> However, this is the Maven mailing list set up for the express
> purpose of getting help with this software.
it is absolutely intended to ask here and I'm your opinion, cause this
is User Mailing list...
> Where else do you suggest I go?
Very good question...Unfortunately i haven't got a idea to suggest...
>
> As for the volunteer service you provide, I thank you for that service.
> But when I am dissatisfied with the service I am getting,
> please don't throw in my face that you are a volunteer.
> You made that choice.
> And as a result, putting up with frustrated customers
> is something you are going to have to deal with.
> It's part of the deal you signed on to when you volunteered.
> If you are not willing to do that,
> then maybe you should consider not volunteering.
Yes exactly the point.
If those who ansered here and don't like to answer or if they are the
opinion to waste their time..than really keep quiet..and let others do
the job...
>
> Now I was told by a responder on this thread that I
> am not a customer because I did not pay for this software.
> Nothing could be further from the truth.
There is no one paying for Maven it self...
> In my career I had many "customers" that did not pay for
> the software I was supporting.
> It was my job to provide them the best support that I could.
> I suggest that responders to requests for help on this
> mailing list adopt the same approach, volunteer or not.
Yes...true...
>
> Another responder to this thread brought up that
> he was volunteering and I was wasting his time.
If the original poster is wasting his/here time than just simply don't
do it anymore...
> How about the time of mine he wasted when he suggested
> I try something that made no difference in the outcome,
> and had nothing to do with the problem?
> And this has happened to me before with other
> responders on this mailing list.
>I was in fact told by another responder that the reply of a specific
person
> was off topic and is often the case for that person.
>
> Maybe you should spend some time pointing that out to those individuals
> rather than chastising someone who is simply trying to get help.
>
> Regards,
> Mike
I'm really sorry Michael to read such things in the user mailing list
which is intended for people using Maven and searching for help and
usage of Maven.
To be honest if someone on the user list is the opinion to waste
here/his time just simple keep quiet...or better unsubscribe from the
list...
Maven is an open source project which lives from its community...and
unfortunately i have to say that is not a good attitude of a "community"
against a user....who searches for help...
I never thought i need to write something like this....
Kind regards
Karl Heinz Marbaise
Apache Maven PMC Member
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Manfred,
With all due respect I insulted no one. Am I frustrated? Yes, but I did not insult anyone.
Now I was perfectly fine with letting this go until I received your comment. So let me use this opportunity to make a few more comments.
Thank you for suggesting That I go somewhere else for help. However, this is the Maven mailing list set up for the express purpose of getting help with this software. Where else do you suggest I go?
As for the volunteer service you provide, I thank you for that service. But when I am dissatisfied with the service I am getting, please don't throw in my face that you are a volunteer. You made that choice. And as a result, putting up with frustrated customers is something you are going to have to deal with. It's part of the deal you signed on to when you volunteered. If you are not willing to do that, then maybe you should consider not volunteering.
Now I was told by a responder on this thread that I am not a customer because I did not pay for this software. Nothing could be further from the truth. In my career I had many "customers" that did not pay for the software I was supporting. It was my job to provide them the best support that I could. I suggest that responders to requests for help on this mailing list adopt the same approach, volunteer or not.
Another responder to this thread brought up that he was volunteering and I was wasting his time. How about the time of mine he wasted when he suggested I try something that made no difference in the outcome, and had nothing to do with the problem? And this has happened to me before with other responders on this mailing list. I was in fact told by another responder that the reply of a specific person was off topic and is often the case for that person.
Maybe you should spend some time pointing that out to those individuals rather than chastising someone who is simply trying to get help.
Regards,
Mike
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Manfred Moser [mailto:manfred@simpligility.com]
Sent: Monday, October 05, 2015 6:56 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Michael,
Please refrain from insulting the efforts of the people on this list trying to help you. If you are not happy with the help you receive here, you are free to look for it elsewhere. I would like the discussions here to stay civil and on topic.
I hope you provide us all here with the same respect that you would expect us to have towards you.
We are all volunteers here.
Thank you
Manfred
Michael.CTR.Tarullo@faa.gov wrote on 2015-10-05 15:28:
> That is fine with me, because your either wrong or incomprehensible
> answers are wasting my time.
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 6:23 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
> > What are you talking about?
> >
> > Of course I don't pay. It's an open source product.
>
> OK, then I don't answer anymore, because it's my free time and you're
> wasting it.
>
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Manfred Moser <ma...@simpligility.com>.
Michael,
Please refrain from insulting the efforts of the people on this list trying
to help you. If you are not happy with the help you receive here, you are
free to look for it elsewhere. I would like the discussions here to stay
civil and on topic.
I hope you provide us all here with the same respect that you would expect
us to have towards you.
We are all volunteers here.
Thank you
Manfred
Michael.CTR.Tarullo@faa.gov wrote on 2015-10-05 15:28:
> That is fine with me, because your either wrong or incomprehensible
> answers are
> wasting my time.
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 6:23 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
> > What are you talking about?
> >
> > Of course I don't pay. It's an open source product.
>
> OK, then I don't answer anymore, because it's my free time and you're
> wasting it.
>
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
That is fine with me, because your either wrong or incomprehensible answers are wasting my time.
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.schaible@gmx.de]
Sent: Monday, October 05, 2015 6:23 PM
To: users@maven.apache.org
Subject: RE: Copy-dependencies goal error
Michael.CTR.Tarullo@faa.gov wrote:
> What are you talking about?
>
> Of course I don't pay. It's an open source product.
OK, then I don't answer anymore, because it's my free time and you're wasting it.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@gmx.de>.
Michael.CTR.Tarullo@faa.gov wrote:
> What are you talking about?
>
> Of course I don't pay. It's an open source product.
OK, then I don't answer anymore, because it's my free time and you're
wasting it.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
What are you talking about?
Of course I don't pay. It's an open source product. That's the business model today, right.... use open source and save money on software development costs. Of course until you have to get help with the product or try and read what is almost always a poor excuse for documentation as is the case with Maven.
But your attitude is wonderful. Just stick in the exclusion and be done. Right, until there is something else that breaks that can't be fixed because you've done nothing to educate your users about how to use the product. And then of course, because I am not paying (or my organization is not paying) then I have to rely on these mailing list which are a poor excuse for support. Your attitude is a perfect example of this. For instance this.... "me and Jörg did explain to you that maven always resolves all dependemcies (unless you exclude them), so there is your education". That is not an explanation, it's just a statement.
And Jorg was of absolutely no help. Look at my other posts. I wasted the whole day running this with other versions to no avail.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: ecki@zusammenkunft.net [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:47 PM
To: Maven Users List
Subject: RE: Copy-dependencies goal error
First of all you dont pay, you only demand (with multiple exclamationmarks), so you are not a customer, and secondly me and Jörg did explain to you that maven always resolves all dependemcies (unless you exclude them), so there is your education. If you dont care about maven just stick in the exclusion and be done.
Bye
Bernd
-----Original Message-----
From: Michael.CTR.Tarullo@faa.gov
To: users@maven.apache.org
Sent: Mo., 05 Okt. 2015 23:42
Subject: RE: Copy-dependencies goal error
Here is why I care:
Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
The problem you are having is because...... <provide an explanation here that someone who is not a contributor or even an intermediate or advanced user can understand>
Here is what you need to do to fix that problem..... <provide the fix and explain why this fix is needed in this case>
You have done nothing to educate the user and to make them more self-sufficient.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:12 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Am Mon, 5 Oct 2015 21:08:02 +0000
schrieb <Mi...@faa.gov>:
> Answer a simple question for me, are you a Maven contributor?
I fixed your stupid pom, so why would you care?
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by ec...@zusammenkunft.net.
First of all you dont pay, you only demand (with multiple exclamationmarks), so you are not a customer, and secondly me and Jörg did explain to you that maven always resolves all dependemcies (unless you exclude them), so there is your education. If you dont care about maven just stick in the exclusion and be done.
Bye
Bernd
-----Original Message-----
From: Michael.CTR.Tarullo@faa.gov
To: users@maven.apache.org
Sent: Mo., 05 Okt. 2015 23:42
Subject: RE: Copy-dependencies goal error
Here is why I care:
Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
The problem you are having is because...... <provide an explanation here that someone who is not a contributor or even an intermediate or advanced user can understand>
Here is what you need to do to fix that problem..... <provide the fix and explain why this fix is needed in this case>
You have done nothing to educate the user and to make them more self-sufficient.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:12 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Am Mon, 5 Oct 2015 21:08:02 +0000
schrieb <Mi...@faa.gov>:
> Answer a simple question for me, are you a Maven contributor?
I fixed your stupid pom, so why would you care?
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Dan Tran <da...@gmail.com>.
If a bunch of ppl are giving me the same feedback. I would step back and
have my ears wide open
-Dan
We have two ears and one mouth so that we can listen twice as much as we
speak.
Epictetus <http://www.brainyquote.com/quotes/authors/e/epictetus.html>
On Tue, Oct 6, 2015 at 1:19 PM, Curtis Rueden <ct...@wisc.edu> wrote:
> Hi Wayne,
>
> > I'm glad Greg was able to help you solve your problem.
>
> Greg's response was great. But in fairness, it was Bernd who actually
> stated the solution to Michael's problem. It would be nice if this thread
> could wrap up with Michael acknowledging that Bernd's fix actually does the
> job.
>
> Regards,
> Curtis
>
> On Tue, Oct 6, 2015 at 3:11 PM, Wayne Fay <wa...@gmail.com> wrote:
>
> > If you disagree with almost everything I said, there's really no point
> > in continuing to discuss it. The possibility of either of us being
> > convinced to change our minds is vanishingly small.
> >
> > I'm glad Greg was able to help you solve your problem.
> >
> > Respectfully,
> > Wayne
> >
> > On Tue, Oct 6, 2015 at 2:17 PM, <Mi...@faa.gov> wrote:
> > > Wayne,
> > >
> > > Thank you for your reply. I think I disagree with almost everything
> you
> > said.
> > >
> > > First I did not attack anyone. Was my attitude bad, yes. Did it get
> > worse when I felt like I was not getting the explanation I needed, most
> > assuredly. I called no one a name, nor insulted anyone's intelligence,
> and
> > when I came close to it I apologized. That's more than I got from
> several
> > of the responders. Just check the thread, its all there.
> > >
> > > Second, are you implying that you only support people that are happy
> > with the product? It sounds to me that you are on the defensive already
> > and as soon as you get someone that is frustrated or displeased. Like
> it
> > is somehow their fault.
> > >
> > > Third, how do you know how much time I've invested in trying to learn
> > Maven? How much is enough before I can have this "intelligent" Maven
> > dialog with the Maven community? Users don't want to ask people for help
> > (i.e. at least I like to try and figure things out for myself), but there
> > comes a time when you are just plain stuck. Maybe its because of a
> mental
> > block and maybe something you've read and researched just does not make
> any
> > sense. Yes I understand that there are some people that probably post
> > questions without having made an effort to learn anything. How do you
> > determine that? How do you differentiate someone who has made an effort
> > from someone who is just trying to get an easy answer?
> > >
> > > With respect to vocabulary and the lingua franca, does "bogus" fit in
> > that category.
> > >
> > > Your comment about the Maven 4.0.0 POM model is particularly
> > frustrating. When you told me to do the research on the original
> version I
> > did exactly as you instructed. That is how I determined that it was
> > 2.2.1. I'm sorry but I think the POM model version question is valid.
> In
> > your original reply you did not know the time frame. I replied to you
> that
> > it goes back at least five years. You did not respond. So while I was
> > doing the research on the version and I found out it was 2.2.1 I thought
> > the POM model version could be a problem. To tell me now after the fact
> > that I should not have been concerned would mean that I would either have
> > to assume that you know that or I would have to be a mind reader.
> > >
> > > And finally I demanded nothing from anyone. I asked if two of the
> > repliers were contributors, and I reiterated a basic question I asked
> from
> > the beginning, several times.
> > >
> > > Yes I am partly to blame here. But many of the Maven User List
> > responders have a little dirt on their hands too. I don't see any of you
> > acknowledging that.
> > >
> > > Regards,
> > > Mike
> > >
> > > Michael Tarullo
> > > Contractor (Engility Corp)
> > > Enterprise Architect
> > > NSRR System Administrator
> > > FAA WJH Technical Center
> > > (609)485-5294
> > >
> > >
> > > -----Original Message-----
> > > From: Wayne Fay [mailto:waynefay@gmail.com]
> > > Sent: Tuesday, October 06, 2015 12:30 PM
> > > To: Maven Users List
> > > Subject: Re: Copy-dependencies goal error
> > >
> > > Maven is a rather complex piece of software. Many problems cannot be
> > simply distilled to "here's your simple problem, and here's your simple
> > solution." I understand this is what you want, but it is rarely that
> > simple. And attacking the people on this list who are trying to help you
> > when you are frustrated with the type of support they are providing is a
> > really bad approach to problem solving. Also recognize that many people
> on
> > this list are not US-born native English speakers, so there is sometimes
> a
> > language barrier even when we are all writing English.
> > >
> > > By using a free product, you (and your employer) should recognize that
> > you are trading off dollar costs for other costs - including your own
> time.
> > Please don't complain about people asking you to do something very simple
> > like install a couple other versions to see if that fixes your build
> issue.
> > It doesn't sound like you went back and tried 2.2.1 as I originally
> > recommended - simply to get more information about what happened,
> certainly
> > not intending to guarantee that would fix your issue. I'd be curious
> about
> > the error message you say that you got in 3.0.5.
> > >
> > > (Also, as a side-note, the POM model has been 4.0.0 for a long time -
> if
> > I was worried about that, I would have mentioned it. This is where "not
> > really knowing the product at all, and not wanting to" becomes a problem,
> > you are making bad assumptions.)
> > >
> > > And yes, the users of this list generally expect people to have some
> > passing familiarity with the product and the lingua franca that is
> > utilized. There are several free resources online to help you "get up to
> > speed" in the form of user's manuals etc. Your response here will most
> > likely be "but I don't want to learn Maven, I just need to use it for
> this
> > quick thing in my job so just help me with that" and the collective
> answer
> > here will be "but Maven is complex, there are so many variables,
> providing
> > simple solutions to problems is even tougher when the user lacks the
> > standard foundational knowledge that is typical."
> > >
> > > It is fine that you only use Maven for your job and thus don't want to
> > learn much - just get your issue fixed. Please understand that our
> > collective tolerance for such users, when they have the wrong attitude as
> > you have demonstrated in this thread, is pretty low. Especially when you
> > say this is part of a COTS software which means that vendor is "passing
> the
> > buck" for support to this list when they themselves should provide you
> more
> > support which you are paying for. In the ideal scenario, you open a
> ticket
> > to that vendor, they have an internal person who is good with Maven who
> > provides you with support, and only if they cannot solve the problem
> would
> > they come to this list for support on your behalf.
> > >
> > > You should not be unhappy with the users of this list. You should
> direct
> > that anger to the COTS vendor who is failing to provide you with support
> > for a product that you have paid for! If your emails to this list
> > demonstrates how angry you get when you haven't paid for something and
> > don't get what you expect, I don't want to be around when we throw
> > substantial real dollars into the mix - I anticipate a stream of
> > obscenity-laced emails flying in every direction.
> > >
> > > Demanding short & simple responses to all inquiries such as yours will
> > result in little traffic on this list as there is rarely a short & simple
> > response to most of the questions. And yes, demanding is the only word
> > which is appropriate in the context of this thread.
> > >
> > > We're happy to (try to) support you here, but I'd suggest that you
> adopt
> > a somewhat different approach & attitude first.
> > >
> > > Thanks,
> > > Wayne
> > > Apache Maven PMC Member
> > >
> > > On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
> > >> Here is why I care:
> > >>
> > >> Well I'm not a Maven contributor. I don't wish to be. I don't even
> > want to use the product, and wouldn't if I wasn't required to for my job.
> > >>
> > >> So I get the impression that certain people answer questions because
> > they are contributors and answer the question as if everyone else is a
> > contributor and is expected to know the product as such.
> > >>
> > >> You folks in the open source arena have a lot to learn. Your reply
> > that you "fixed my stupid pom" is one of those things. Good customer
> > support would go something like this.....
> > >>
> > >> The problem you are having is because...... <provide an explanation
> > >> here that someone who is not a contributor or even an intermediate or
> > >> advanced user can understand>
> > >>
> > >> Here is what you need to do to fix that problem..... <provide the fix
> > >> and explain why this fix is needed in this case>
> > >>
> > >> You have done nothing to educate the user and to make them more
> > self-sufficient.
> > >>
> > >> Michael Tarullo
> > >> Contractor (Engility Corp)
> > >> Enterprise Architect
> > >> NSRR System Administrator
> > >> FAA WJH Technical Center
> > >> (609)485-5294
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> > >> Sent: Monday, October 05, 2015 5:12 PM
> > >> To: users@maven.apache.org
> > >> Subject: Re: Copy-dependencies goal error
> > >>
> > >> Am Mon, 5 Oct 2015 21:08:02 +0000
> > >> schrieb <Mi...@faa.gov>:
> > >>> Answer a simple question for me, are you a Maven contributor?
> > >>
> > >> I fixed your stupid pom, so why would you care?
> > >>
> > >> Gruss
> > >> Bernd
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Curtis,
I would be more than happy to acknowledge that. I'm glad you brought that up, it was my intention to do so. In fact I was drafting such a response when I received bit Greg's and Wayne's reply and thought it more important to reply to them first.
This actually raises another point, but to be honest I see no reason to even make it at this time.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: ctrueden.wisc@gmail.com [mailto:ctrueden.wisc@gmail.com] On Behalf Of Curtis Rueden
Sent: Tuesday, October 06, 2015 4:19 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Hi Wayne,
> I'm glad Greg was able to help you solve your problem.
Greg's response was great. But in fairness, it was Bernd who actually stated the solution to Michael's problem. It would be nice if this thread could wrap up with Michael acknowledging that Bernd's fix actually does the job.
Regards,
Curtis
On Tue, Oct 6, 2015 at 3:11 PM, Wayne Fay <wa...@gmail.com> wrote:
> If you disagree with almost everything I said, there's really no point
> in continuing to discuss it. The possibility of either of us being
> convinced to change our minds is vanishingly small.
>
> I'm glad Greg was able to help you solve your problem.
>
> Respectfully,
> Wayne
>
> On Tue, Oct 6, 2015 at 2:17 PM, <Mi...@faa.gov> wrote:
> > Wayne,
> >
> > Thank you for your reply. I think I disagree with almost everything
> > you
> said.
> >
> > First I did not attack anyone. Was my attitude bad, yes. Did it
> > get
> worse when I felt like I was not getting the explanation I needed,
> most assuredly. I called no one a name, nor insulted anyone's
> intelligence, and when I came close to it I apologized. That's more
> than I got from several of the responders. Just check the thread, its all there.
> >
> > Second, are you implying that you only support people that are happy
> with the product? It sounds to me that you are on the defensive already
> and as soon as you get someone that is frustrated or displeased. Like it
> is somehow their fault.
> >
> > Third, how do you know how much time I've invested in trying to
> > learn
> Maven? How much is enough before I can have this "intelligent" Maven
> dialog with the Maven community? Users don't want to ask people for
> help (i.e. at least I like to try and figure things out for myself),
> but there comes a time when you are just plain stuck. Maybe its
> because of a mental block and maybe something you've read and
> researched just does not make any sense. Yes I understand that there
> are some people that probably post questions without having made an
> effort to learn anything. How do you determine that? How do you
> differentiate someone who has made an effort from someone who is just trying to get an easy answer?
> >
> > With respect to vocabulary and the lingua franca, does "bogus" fit
> > in
> that category.
> >
> > Your comment about the Maven 4.0.0 POM model is particularly
> frustrating. When you told me to do the research on the original
> version I did exactly as you instructed. That is how I determined
> that it was 2.2.1. I'm sorry but I think the POM model version
> question is valid. In your original reply you did not know the time
> frame. I replied to you that it goes back at least five years. You
> did not respond. So while I was doing the research on the version and
> I found out it was 2.2.1 I thought the POM model version could be a
> problem. To tell me now after the fact that I should not have been
> concerned would mean that I would either have to assume that you know that or I would have to be a mind reader.
> >
> > And finally I demanded nothing from anyone. I asked if two of the
> repliers were contributors, and I reiterated a basic question I asked
> from the beginning, several times.
> >
> > Yes I am partly to blame here. But many of the Maven User List
> responders have a little dirt on their hands too. I don't see any of
> you acknowledging that.
> >
> > Regards,
> > Mike
> >
> > Michael Tarullo
> > Contractor (Engility Corp)
> > Enterprise Architect
> > NSRR System Administrator
> > FAA WJH Technical Center
> > (609)485-5294
> >
> >
> > -----Original Message-----
> > From: Wayne Fay [mailto:waynefay@gmail.com]
> > Sent: Tuesday, October 06, 2015 12:30 PM
> > To: Maven Users List
> > Subject: Re: Copy-dependencies goal error
> >
> > Maven is a rather complex piece of software. Many problems cannot be
> simply distilled to "here's your simple problem, and here's your
> simple solution." I understand this is what you want, but it is rarely
> that simple. And attacking the people on this list who are trying to
> help you when you are frustrated with the type of support they are
> providing is a really bad approach to problem solving. Also recognize
> that many people on this list are not US-born native English speakers,
> so there is sometimes a language barrier even when we are all writing English.
> >
> > By using a free product, you (and your employer) should recognize
> > that
> you are trading off dollar costs for other costs - including your own time.
> Please don't complain about people asking you to do something very
> simple like install a couple other versions to see if that fixes your build issue.
> It doesn't sound like you went back and tried 2.2.1 as I originally
> recommended - simply to get more information about what happened,
> certainly not intending to guarantee that would fix your issue. I'd be
> curious about the error message you say that you got in 3.0.5.
> >
> > (Also, as a side-note, the POM model has been 4.0.0 for a long time
> > - if
> I was worried about that, I would have mentioned it. This is where
> "not really knowing the product at all, and not wanting to" becomes a
> problem, you are making bad assumptions.)
> >
> > And yes, the users of this list generally expect people to have some
> passing familiarity with the product and the lingua franca that is
> utilized. There are several free resources online to help you "get up
> to speed" in the form of user's manuals etc. Your response here will
> most likely be "but I don't want to learn Maven, I just need to use it
> for this quick thing in my job so just help me with that" and the
> collective answer here will be "but Maven is complex, there are so
> many variables, providing simple solutions to problems is even tougher
> when the user lacks the standard foundational knowledge that is typical."
> >
> > It is fine that you only use Maven for your job and thus don't want
> > to
> learn much - just get your issue fixed. Please understand that our
> collective tolerance for such users, when they have the wrong attitude
> as you have demonstrated in this thread, is pretty low. Especially
> when you say this is part of a COTS software which means that vendor
> is "passing the buck" for support to this list when they themselves
> should provide you more support which you are paying for. In the ideal
> scenario, you open a ticket to that vendor, they have an internal
> person who is good with Maven who provides you with support, and only
> if they cannot solve the problem would they come to this list for support on your behalf.
> >
> > You should not be unhappy with the users of this list. You should
> > direct
> that anger to the COTS vendor who is failing to provide you with
> support for a product that you have paid for! If your emails to this
> list demonstrates how angry you get when you haven't paid for
> something and don't get what you expect, I don't want to be around
> when we throw substantial real dollars into the mix - I anticipate a
> stream of obscenity-laced emails flying in every direction.
> >
> > Demanding short & simple responses to all inquiries such as yours
> > will
> result in little traffic on this list as there is rarely a short &
> simple response to most of the questions. And yes, demanding is the
> only word which is appropriate in the context of this thread.
> >
> > We're happy to (try to) support you here, but I'd suggest that you
> > adopt
> a somewhat different approach & attitude first.
> >
> > Thanks,
> > Wayne
> > Apache Maven PMC Member
> >
> > On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
> >> Here is why I care:
> >>
> >> Well I'm not a Maven contributor. I don't wish to be. I don't
> >> even
> want to use the product, and wouldn't if I wasn't required to for my job.
> >>
> >> So I get the impression that certain people answer questions
> >> because
> they are contributors and answer the question as if everyone else is a
> contributor and is expected to know the product as such.
> >>
> >> You folks in the open source arena have a lot to learn. Your reply
> that you "fixed my stupid pom" is one of those things. Good customer
> support would go something like this.....
> >>
> >> The problem you are having is because...... <provide an explanation
> >> here that someone who is not a contributor or even an intermediate
> >> or advanced user can understand>
> >>
> >> Here is what you need to do to fix that problem..... <provide the
> >> fix and explain why this fix is needed in this case>
> >>
> >> You have done nothing to educate the user and to make them more
> self-sufficient.
> >>
> >> Michael Tarullo
> >> Contractor (Engility Corp)
> >> Enterprise Architect
> >> NSRR System Administrator
> >> FAA WJH Technical Center
> >> (609)485-5294
> >>
> >>
> >> -----Original Message-----
> >> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> >> Sent: Monday, October 05, 2015 5:12 PM
> >> To: users@maven.apache.org
> >> Subject: Re: Copy-dependencies goal error
> >>
> >> Am Mon, 5 Oct 2015 21:08:02 +0000
> >> schrieb <Mi...@faa.gov>:
> >>> Answer a simple question for me, are you a Maven contributor?
> >>
> >> I fixed your stupid pom, so why would you care?
> >>
> >> Gruss
> >> Bernd
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Copy-dependencies goal error
Posted by Curtis Rueden <ct...@wisc.edu>.
Hi Wayne,
> I'm glad Greg was able to help you solve your problem.
Greg's response was great. But in fairness, it was Bernd who actually
stated the solution to Michael's problem. It would be nice if this thread
could wrap up with Michael acknowledging that Bernd's fix actually does the
job.
Regards,
Curtis
On Tue, Oct 6, 2015 at 3:11 PM, Wayne Fay <wa...@gmail.com> wrote:
> If you disagree with almost everything I said, there's really no point
> in continuing to discuss it. The possibility of either of us being
> convinced to change our minds is vanishingly small.
>
> I'm glad Greg was able to help you solve your problem.
>
> Respectfully,
> Wayne
>
> On Tue, Oct 6, 2015 at 2:17 PM, <Mi...@faa.gov> wrote:
> > Wayne,
> >
> > Thank you for your reply. I think I disagree with almost everything you
> said.
> >
> > First I did not attack anyone. Was my attitude bad, yes. Did it get
> worse when I felt like I was not getting the explanation I needed, most
> assuredly. I called no one a name, nor insulted anyone's intelligence, and
> when I came close to it I apologized. That's more than I got from several
> of the responders. Just check the thread, its all there.
> >
> > Second, are you implying that you only support people that are happy
> with the product? It sounds to me that you are on the defensive already
> and as soon as you get someone that is frustrated or displeased. Like it
> is somehow their fault.
> >
> > Third, how do you know how much time I've invested in trying to learn
> Maven? How much is enough before I can have this "intelligent" Maven
> dialog with the Maven community? Users don't want to ask people for help
> (i.e. at least I like to try and figure things out for myself), but there
> comes a time when you are just plain stuck. Maybe its because of a mental
> block and maybe something you've read and researched just does not make any
> sense. Yes I understand that there are some people that probably post
> questions without having made an effort to learn anything. How do you
> determine that? How do you differentiate someone who has made an effort
> from someone who is just trying to get an easy answer?
> >
> > With respect to vocabulary and the lingua franca, does "bogus" fit in
> that category.
> >
> > Your comment about the Maven 4.0.0 POM model is particularly
> frustrating. When you told me to do the research on the original version I
> did exactly as you instructed. That is how I determined that it was
> 2.2.1. I'm sorry but I think the POM model version question is valid. In
> your original reply you did not know the time frame. I replied to you that
> it goes back at least five years. You did not respond. So while I was
> doing the research on the version and I found out it was 2.2.1 I thought
> the POM model version could be a problem. To tell me now after the fact
> that I should not have been concerned would mean that I would either have
> to assume that you know that or I would have to be a mind reader.
> >
> > And finally I demanded nothing from anyone. I asked if two of the
> repliers were contributors, and I reiterated a basic question I asked from
> the beginning, several times.
> >
> > Yes I am partly to blame here. But many of the Maven User List
> responders have a little dirt on their hands too. I don't see any of you
> acknowledging that.
> >
> > Regards,
> > Mike
> >
> > Michael Tarullo
> > Contractor (Engility Corp)
> > Enterprise Architect
> > NSRR System Administrator
> > FAA WJH Technical Center
> > (609)485-5294
> >
> >
> > -----Original Message-----
> > From: Wayne Fay [mailto:waynefay@gmail.com]
> > Sent: Tuesday, October 06, 2015 12:30 PM
> > To: Maven Users List
> > Subject: Re: Copy-dependencies goal error
> >
> > Maven is a rather complex piece of software. Many problems cannot be
> simply distilled to "here's your simple problem, and here's your simple
> solution." I understand this is what you want, but it is rarely that
> simple. And attacking the people on this list who are trying to help you
> when you are frustrated with the type of support they are providing is a
> really bad approach to problem solving. Also recognize that many people on
> this list are not US-born native English speakers, so there is sometimes a
> language barrier even when we are all writing English.
> >
> > By using a free product, you (and your employer) should recognize that
> you are trading off dollar costs for other costs - including your own time.
> Please don't complain about people asking you to do something very simple
> like install a couple other versions to see if that fixes your build issue.
> It doesn't sound like you went back and tried 2.2.1 as I originally
> recommended - simply to get more information about what happened, certainly
> not intending to guarantee that would fix your issue. I'd be curious about
> the error message you say that you got in 3.0.5.
> >
> > (Also, as a side-note, the POM model has been 4.0.0 for a long time - if
> I was worried about that, I would have mentioned it. This is where "not
> really knowing the product at all, and not wanting to" becomes a problem,
> you are making bad assumptions.)
> >
> > And yes, the users of this list generally expect people to have some
> passing familiarity with the product and the lingua franca that is
> utilized. There are several free resources online to help you "get up to
> speed" in the form of user's manuals etc. Your response here will most
> likely be "but I don't want to learn Maven, I just need to use it for this
> quick thing in my job so just help me with that" and the collective answer
> here will be "but Maven is complex, there are so many variables, providing
> simple solutions to problems is even tougher when the user lacks the
> standard foundational knowledge that is typical."
> >
> > It is fine that you only use Maven for your job and thus don't want to
> learn much - just get your issue fixed. Please understand that our
> collective tolerance for such users, when they have the wrong attitude as
> you have demonstrated in this thread, is pretty low. Especially when you
> say this is part of a COTS software which means that vendor is "passing the
> buck" for support to this list when they themselves should provide you more
> support which you are paying for. In the ideal scenario, you open a ticket
> to that vendor, they have an internal person who is good with Maven who
> provides you with support, and only if they cannot solve the problem would
> they come to this list for support on your behalf.
> >
> > You should not be unhappy with the users of this list. You should direct
> that anger to the COTS vendor who is failing to provide you with support
> for a product that you have paid for! If your emails to this list
> demonstrates how angry you get when you haven't paid for something and
> don't get what you expect, I don't want to be around when we throw
> substantial real dollars into the mix - I anticipate a stream of
> obscenity-laced emails flying in every direction.
> >
> > Demanding short & simple responses to all inquiries such as yours will
> result in little traffic on this list as there is rarely a short & simple
> response to most of the questions. And yes, demanding is the only word
> which is appropriate in the context of this thread.
> >
> > We're happy to (try to) support you here, but I'd suggest that you adopt
> a somewhat different approach & attitude first.
> >
> > Thanks,
> > Wayne
> > Apache Maven PMC Member
> >
> > On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
> >> Here is why I care:
> >>
> >> Well I'm not a Maven contributor. I don't wish to be. I don't even
> want to use the product, and wouldn't if I wasn't required to for my job.
> >>
> >> So I get the impression that certain people answer questions because
> they are contributors and answer the question as if everyone else is a
> contributor and is expected to know the product as such.
> >>
> >> You folks in the open source arena have a lot to learn. Your reply
> that you "fixed my stupid pom" is one of those things. Good customer
> support would go something like this.....
> >>
> >> The problem you are having is because...... <provide an explanation
> >> here that someone who is not a contributor or even an intermediate or
> >> advanced user can understand>
> >>
> >> Here is what you need to do to fix that problem..... <provide the fix
> >> and explain why this fix is needed in this case>
> >>
> >> You have done nothing to educate the user and to make them more
> self-sufficient.
> >>
> >> Michael Tarullo
> >> Contractor (Engility Corp)
> >> Enterprise Architect
> >> NSRR System Administrator
> >> FAA WJH Technical Center
> >> (609)485-5294
> >>
> >>
> >> -----Original Message-----
> >> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> >> Sent: Monday, October 05, 2015 5:12 PM
> >> To: users@maven.apache.org
> >> Subject: Re: Copy-dependencies goal error
> >>
> >> Am Mon, 5 Oct 2015 21:08:02 +0000
> >> schrieb <Mi...@faa.gov>:
> >>> Answer a simple question for me, are you a Maven contributor?
> >>
> >> I fixed your stupid pom, so why would you care?
> >>
> >> Gruss
> >> Bernd
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
And that just about sums it up!
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Tuesday, October 06, 2015 4:11 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
If you disagree with almost everything I said, there's really no point in continuing to discuss it. The possibility of either of us being convinced to change our minds is vanishingly small.
I'm glad Greg was able to help you solve your problem.
Respectfully,
Wayne
On Tue, Oct 6, 2015 at 2:17 PM, <Mi...@faa.gov> wrote:
> Wayne,
>
> Thank you for your reply. I think I disagree with almost everything you said.
>
> First I did not attack anyone. Was my attitude bad, yes. Did it get worse when I felt like I was not getting the explanation I needed, most assuredly. I called no one a name, nor insulted anyone's intelligence, and when I came close to it I apologized. That's more than I got from several of the responders. Just check the thread, its all there.
>
> Second, are you implying that you only support people that are happy with the product? It sounds to me that you are on the defensive already and as soon as you get someone that is frustrated or displeased. Like it is somehow their fault.
>
> Third, how do you know how much time I've invested in trying to learn Maven? How much is enough before I can have this "intelligent" Maven dialog with the Maven community? Users don't want to ask people for help (i.e. at least I like to try and figure things out for myself), but there comes a time when you are just plain stuck. Maybe its because of a mental block and maybe something you've read and researched just does not make any sense. Yes I understand that there are some people that probably post questions without having made an effort to learn anything. How do you determine that? How do you differentiate someone who has made an effort from someone who is just trying to get an easy answer?
>
> With respect to vocabulary and the lingua franca, does "bogus" fit in that category.
>
> Your comment about the Maven 4.0.0 POM model is particularly frustrating. When you told me to do the research on the original version I did exactly as you instructed. That is how I determined that it was 2.2.1. I'm sorry but I think the POM model version question is valid. In your original reply you did not know the time frame. I replied to you that it goes back at least five years. You did not respond. So while I was doing the research on the version and I found out it was 2.2.1 I thought the POM model version could be a problem. To tell me now after the fact that I should not have been concerned would mean that I would either have to assume that you know that or I would have to be a mind reader.
>
> And finally I demanded nothing from anyone. I asked if two of the repliers were contributors, and I reiterated a basic question I asked from the beginning, several times.
>
> Yes I am partly to blame here. But many of the Maven User List responders have a little dirt on their hands too. I don't see any of you acknowledging that.
>
> Regards,
> Mike
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Tuesday, October 06, 2015 12:30 PM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Maven is a rather complex piece of software. Many problems cannot be simply distilled to "here's your simple problem, and here's your simple solution." I understand this is what you want, but it is rarely that simple. And attacking the people on this list who are trying to help you when you are frustrated with the type of support they are providing is a really bad approach to problem solving. Also recognize that many people on this list are not US-born native English speakers, so there is sometimes a language barrier even when we are all writing English.
>
> By using a free product, you (and your employer) should recognize that you are trading off dollar costs for other costs - including your own time. Please don't complain about people asking you to do something very simple like install a couple other versions to see if that fixes your build issue. It doesn't sound like you went back and tried 2.2.1 as I originally recommended - simply to get more information about what happened, certainly not intending to guarantee that would fix your issue. I'd be curious about the error message you say that you got in 3.0.5.
>
> (Also, as a side-note, the POM model has been 4.0.0 for a long time -
> if I was worried about that, I would have mentioned it. This is where
> "not really knowing the product at all, and not wanting to" becomes a
> problem, you are making bad assumptions.)
>
> And yes, the users of this list generally expect people to have some passing familiarity with the product and the lingua franca that is utilized. There are several free resources online to help you "get up to speed" in the form of user's manuals etc. Your response here will most likely be "but I don't want to learn Maven, I just need to use it for this quick thing in my job so just help me with that" and the collective answer here will be "but Maven is complex, there are so many variables, providing simple solutions to problems is even tougher when the user lacks the standard foundational knowledge that is typical."
>
> It is fine that you only use Maven for your job and thus don't want to learn much - just get your issue fixed. Please understand that our collective tolerance for such users, when they have the wrong attitude as you have demonstrated in this thread, is pretty low. Especially when you say this is part of a COTS software which means that vendor is "passing the buck" for support to this list when they themselves should provide you more support which you are paying for. In the ideal scenario, you open a ticket to that vendor, they have an internal person who is good with Maven who provides you with support, and only if they cannot solve the problem would they come to this list for support on your behalf.
>
> You should not be unhappy with the users of this list. You should direct that anger to the COTS vendor who is failing to provide you with support for a product that you have paid for! If your emails to this list demonstrates how angry you get when you haven't paid for something and don't get what you expect, I don't want to be around when we throw substantial real dollars into the mix - I anticipate a stream of obscenity-laced emails flying in every direction.
>
> Demanding short & simple responses to all inquiries such as yours will result in little traffic on this list as there is rarely a short & simple response to most of the questions. And yes, demanding is the only word which is appropriate in the context of this thread.
>
> We're happy to (try to) support you here, but I'd suggest that you adopt a somewhat different approach & attitude first.
>
> Thanks,
> Wayne
> Apache Maven PMC Member
>
> On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
>> Here is why I care:
>>
>> Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
>>
>> So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
>>
>> You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
>>
>> The problem you are having is because...... <provide an explanation
>> here that someone who is not a contributor or even an intermediate or
>> advanced user can understand>
>>
>> Here is what you need to do to fix that problem..... <provide the fix
>> and explain why this fix is needed in this case>
>>
>> You have done nothing to educate the user and to make them more self-sufficient.
>>
>> Michael Tarullo
>> Contractor (Engility Corp)
>> Enterprise Architect
>> NSRR System Administrator
>> FAA WJH Technical Center
>> (609)485-5294
>>
>>
>> -----Original Message-----
>> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
>> Sent: Monday, October 05, 2015 5:12 PM
>> To: users@maven.apache.org
>> Subject: Re: Copy-dependencies goal error
>>
>> Am Mon, 5 Oct 2015 21:08:02 +0000
>> schrieb <Mi...@faa.gov>:
>>> Answer a simple question for me, are you a Maven contributor?
>>
>> I fixed your stupid pom, so why would you care?
>>
>> Gruss
>> Bernd
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Wayne Fay <wa...@gmail.com>.
If you disagree with almost everything I said, there's really no point
in continuing to discuss it. The possibility of either of us being
convinced to change our minds is vanishingly small.
I'm glad Greg was able to help you solve your problem.
Respectfully,
Wayne
On Tue, Oct 6, 2015 at 2:17 PM, <Mi...@faa.gov> wrote:
> Wayne,
>
> Thank you for your reply. I think I disagree with almost everything you said.
>
> First I did not attack anyone. Was my attitude bad, yes. Did it get worse when I felt like I was not getting the explanation I needed, most assuredly. I called no one a name, nor insulted anyone's intelligence, and when I came close to it I apologized. That's more than I got from several of the responders. Just check the thread, its all there.
>
> Second, are you implying that you only support people that are happy with the product? It sounds to me that you are on the defensive already and as soon as you get someone that is frustrated or displeased. Like it is somehow their fault.
>
> Third, how do you know how much time I've invested in trying to learn Maven? How much is enough before I can have this "intelligent" Maven dialog with the Maven community? Users don't want to ask people for help (i.e. at least I like to try and figure things out for myself), but there comes a time when you are just plain stuck. Maybe its because of a mental block and maybe something you've read and researched just does not make any sense. Yes I understand that there are some people that probably post questions without having made an effort to learn anything. How do you determine that? How do you differentiate someone who has made an effort from someone who is just trying to get an easy answer?
>
> With respect to vocabulary and the lingua franca, does "bogus" fit in that category.
>
> Your comment about the Maven 4.0.0 POM model is particularly frustrating. When you told me to do the research on the original version I did exactly as you instructed. That is how I determined that it was 2.2.1. I'm sorry but I think the POM model version question is valid. In your original reply you did not know the time frame. I replied to you that it goes back at least five years. You did not respond. So while I was doing the research on the version and I found out it was 2.2.1 I thought the POM model version could be a problem. To tell me now after the fact that I should not have been concerned would mean that I would either have to assume that you know that or I would have to be a mind reader.
>
> And finally I demanded nothing from anyone. I asked if two of the repliers were contributors, and I reiterated a basic question I asked from the beginning, several times.
>
> Yes I am partly to blame here. But many of the Maven User List responders have a little dirt on their hands too. I don't see any of you acknowledging that.
>
> Regards,
> Mike
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Tuesday, October 06, 2015 12:30 PM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Maven is a rather complex piece of software. Many problems cannot be simply distilled to "here's your simple problem, and here's your simple solution." I understand this is what you want, but it is rarely that simple. And attacking the people on this list who are trying to help you when you are frustrated with the type of support they are providing is a really bad approach to problem solving. Also recognize that many people on this list are not US-born native English speakers, so there is sometimes a language barrier even when we are all writing English.
>
> By using a free product, you (and your employer) should recognize that you are trading off dollar costs for other costs - including your own time. Please don't complain about people asking you to do something very simple like install a couple other versions to see if that fixes your build issue. It doesn't sound like you went back and tried 2.2.1 as I originally recommended - simply to get more information about what happened, certainly not intending to guarantee that would fix your issue. I'd be curious about the error message you say that you got in 3.0.5.
>
> (Also, as a side-note, the POM model has been 4.0.0 for a long time - if I was worried about that, I would have mentioned it. This is where "not really knowing the product at all, and not wanting to" becomes a problem, you are making bad assumptions.)
>
> And yes, the users of this list generally expect people to have some passing familiarity with the product and the lingua franca that is utilized. There are several free resources online to help you "get up to speed" in the form of user's manuals etc. Your response here will most likely be "but I don't want to learn Maven, I just need to use it for this quick thing in my job so just help me with that" and the collective answer here will be "but Maven is complex, there are so many variables, providing simple solutions to problems is even tougher when the user lacks the standard foundational knowledge that is typical."
>
> It is fine that you only use Maven for your job and thus don't want to learn much - just get your issue fixed. Please understand that our collective tolerance for such users, when they have the wrong attitude as you have demonstrated in this thread, is pretty low. Especially when you say this is part of a COTS software which means that vendor is "passing the buck" for support to this list when they themselves should provide you more support which you are paying for. In the ideal scenario, you open a ticket to that vendor, they have an internal person who is good with Maven who provides you with support, and only if they cannot solve the problem would they come to this list for support on your behalf.
>
> You should not be unhappy with the users of this list. You should direct that anger to the COTS vendor who is failing to provide you with support for a product that you have paid for! If your emails to this list demonstrates how angry you get when you haven't paid for something and don't get what you expect, I don't want to be around when we throw substantial real dollars into the mix - I anticipate a stream of obscenity-laced emails flying in every direction.
>
> Demanding short & simple responses to all inquiries such as yours will result in little traffic on this list as there is rarely a short & simple response to most of the questions. And yes, demanding is the only word which is appropriate in the context of this thread.
>
> We're happy to (try to) support you here, but I'd suggest that you adopt a somewhat different approach & attitude first.
>
> Thanks,
> Wayne
> Apache Maven PMC Member
>
> On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
>> Here is why I care:
>>
>> Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
>>
>> So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
>>
>> You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
>>
>> The problem you are having is because...... <provide an explanation
>> here that someone who is not a contributor or even an intermediate or
>> advanced user can understand>
>>
>> Here is what you need to do to fix that problem..... <provide the fix
>> and explain why this fix is needed in this case>
>>
>> You have done nothing to educate the user and to make them more self-sufficient.
>>
>> Michael Tarullo
>> Contractor (Engility Corp)
>> Enterprise Architect
>> NSRR System Administrator
>> FAA WJH Technical Center
>> (609)485-5294
>>
>>
>> -----Original Message-----
>> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
>> Sent: Monday, October 05, 2015 5:12 PM
>> To: users@maven.apache.org
>> Subject: Re: Copy-dependencies goal error
>>
>> Am Mon, 5 Oct 2015 21:08:02 +0000
>> schrieb <Mi...@faa.gov>:
>>> Answer a simple question for me, are you a Maven contributor?
>>
>> I fixed your stupid pom, so why would you care?
>>
>> Gruss
>> Bernd
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Wayne,
Thank you for your reply. I think I disagree with almost everything you said.
First I did not attack anyone. Was my attitude bad, yes. Did it get worse when I felt like I was not getting the explanation I needed, most assuredly. I called no one a name, nor insulted anyone's intelligence, and when I came close to it I apologized. That's more than I got from several of the responders. Just check the thread, its all there.
Second, are you implying that you only support people that are happy with the product? It sounds to me that you are on the defensive already and as soon as you get someone that is frustrated or displeased. Like it is somehow their fault.
Third, how do you know how much time I've invested in trying to learn Maven? How much is enough before I can have this "intelligent" Maven dialog with the Maven community? Users don't want to ask people for help (i.e. at least I like to try and figure things out for myself), but there comes a time when you are just plain stuck. Maybe its because of a mental block and maybe something you've read and researched just does not make any sense. Yes I understand that there are some people that probably post questions without having made an effort to learn anything. How do you determine that? How do you differentiate someone who has made an effort from someone who is just trying to get an easy answer?
With respect to vocabulary and the lingua franca, does "bogus" fit in that category.
Your comment about the Maven 4.0.0 POM model is particularly frustrating. When you told me to do the research on the original version I did exactly as you instructed. That is how I determined that it was 2.2.1. I'm sorry but I think the POM model version question is valid. In your original reply you did not know the time frame. I replied to you that it goes back at least five years. You did not respond. So while I was doing the research on the version and I found out it was 2.2.1 I thought the POM model version could be a problem. To tell me now after the fact that I should not have been concerned would mean that I would either have to assume that you know that or I would have to be a mind reader.
And finally I demanded nothing from anyone. I asked if two of the repliers were contributors, and I reiterated a basic question I asked from the beginning, several times.
Yes I am partly to blame here. But many of the Maven User List responders have a little dirt on their hands too. I don't see any of you acknowledging that.
Regards,
Mike
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Tuesday, October 06, 2015 12:30 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Maven is a rather complex piece of software. Many problems cannot be simply distilled to "here's your simple problem, and here's your simple solution." I understand this is what you want, but it is rarely that simple. And attacking the people on this list who are trying to help you when you are frustrated with the type of support they are providing is a really bad approach to problem solving. Also recognize that many people on this list are not US-born native English speakers, so there is sometimes a language barrier even when we are all writing English.
By using a free product, you (and your employer) should recognize that you are trading off dollar costs for other costs - including your own time. Please don't complain about people asking you to do something very simple like install a couple other versions to see if that fixes your build issue. It doesn't sound like you went back and tried 2.2.1 as I originally recommended - simply to get more information about what happened, certainly not intending to guarantee that would fix your issue. I'd be curious about the error message you say that you got in 3.0.5.
(Also, as a side-note, the POM model has been 4.0.0 for a long time - if I was worried about that, I would have mentioned it. This is where "not really knowing the product at all, and not wanting to" becomes a problem, you are making bad assumptions.)
And yes, the users of this list generally expect people to have some passing familiarity with the product and the lingua franca that is utilized. There are several free resources online to help you "get up to speed" in the form of user's manuals etc. Your response here will most likely be "but I don't want to learn Maven, I just need to use it for this quick thing in my job so just help me with that" and the collective answer here will be "but Maven is complex, there are so many variables, providing simple solutions to problems is even tougher when the user lacks the standard foundational knowledge that is typical."
It is fine that you only use Maven for your job and thus don't want to learn much - just get your issue fixed. Please understand that our collective tolerance for such users, when they have the wrong attitude as you have demonstrated in this thread, is pretty low. Especially when you say this is part of a COTS software which means that vendor is "passing the buck" for support to this list when they themselves should provide you more support which you are paying for. In the ideal scenario, you open a ticket to that vendor, they have an internal person who is good with Maven who provides you with support, and only if they cannot solve the problem would they come to this list for support on your behalf.
You should not be unhappy with the users of this list. You should direct that anger to the COTS vendor who is failing to provide you with support for a product that you have paid for! If your emails to this list demonstrates how angry you get when you haven't paid for something and don't get what you expect, I don't want to be around when we throw substantial real dollars into the mix - I anticipate a stream of obscenity-laced emails flying in every direction.
Demanding short & simple responses to all inquiries such as yours will result in little traffic on this list as there is rarely a short & simple response to most of the questions. And yes, demanding is the only word which is appropriate in the context of this thread.
We're happy to (try to) support you here, but I'd suggest that you adopt a somewhat different approach & attitude first.
Thanks,
Wayne
Apache Maven PMC Member
On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
> Here is why I care:
>
> Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
>
> So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
>
> You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
>
> The problem you are having is because...... <provide an explanation
> here that someone who is not a contributor or even an intermediate or
> advanced user can understand>
>
> Here is what you need to do to fix that problem..... <provide the fix
> and explain why this fix is needed in this case>
>
> You have done nothing to educate the user and to make them more self-sufficient.
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 5:12 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Am Mon, 5 Oct 2015 21:08:02 +0000
> schrieb <Mi...@faa.gov>:
>> Answer a simple question for me, are you a Maven contributor?
>
> I fixed your stupid pom, so why would you care?
>
> Gruss
> Bernd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Wayne Fay <wa...@gmail.com>.
Maven is a rather complex piece of software. Many problems cannot be
simply distilled to "here's your simple problem, and here's your
simple solution." I understand this is what you want, but it is rarely
that simple. And attacking the people on this list who are trying to
help you when you are frustrated with the type of support they are
providing is a really bad approach to problem solving. Also recognize
that many people on this list are not US-born native English speakers,
so there is sometimes a language barrier even when we are all writing
English.
By using a free product, you (and your employer) should recognize that
you are trading off dollar costs for other costs - including your own
time. Please don't complain about people asking you to do something
very simple like install a couple other versions to see if that fixes
your build issue. It doesn't sound like you went back and tried 2.2.1
as I originally recommended - simply to get more information about
what happened, certainly not intending to guarantee that would fix
your issue. I'd be curious about the error message you say that you
got in 3.0.5.
(Also, as a side-note, the POM model has been 4.0.0 for a long time -
if I was worried about that, I would have mentioned it. This is where
"not really knowing the product at all, and not wanting to" becomes a
problem, you are making bad assumptions.)
And yes, the users of this list generally expect people to have some
passing familiarity with the product and the lingua franca that is
utilized. There are several free resources online to help you "get up
to speed" in the form of user's manuals etc. Your response here will
most likely be "but I don't want to learn Maven, I just need to use it
for this quick thing in my job so just help me with that" and the
collective answer here will be "but Maven is complex, there are so
many variables, providing simple solutions to problems is even tougher
when the user lacks the standard foundational knowledge that is
typical."
It is fine that you only use Maven for your job and thus don't want to
learn much - just get your issue fixed. Please understand that our
collective tolerance for such users, when they have the wrong attitude
as you have demonstrated in this thread, is pretty low. Especially
when you say this is part of a COTS software which means that vendor
is "passing the buck" for support to this list when they themselves
should provide you more support which you are paying for. In the ideal
scenario, you open a ticket to that vendor, they have an internal
person who is good with Maven who provides you with support, and only
if they cannot solve the problem would they come to this list for
support on your behalf.
You should not be unhappy with the users of this list. You should
direct that anger to the COTS vendor who is failing to provide you
with support for a product that you have paid for! If your emails to
this list demonstrates how angry you get when you haven't paid for
something and don't get what you expect, I don't want to be around
when we throw substantial real dollars into the mix - I anticipate a
stream of obscenity-laced emails flying in every direction.
Demanding short & simple responses to all inquiries such as yours will
result in little traffic on this list as there is rarely a short &
simple response to most of the questions. And yes, demanding is the
only word which is appropriate in the context of this thread.
We're happy to (try to) support you here, but I'd suggest that you
adopt a somewhat different approach & attitude first.
Thanks,
Wayne
Apache Maven PMC Member
On Mon, Oct 5, 2015 at 4:42 PM, <Mi...@faa.gov> wrote:
> Here is why I care:
>
> Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
>
> So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
>
> You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
>
> The problem you are having is because...... <provide an explanation here that someone who is not a contributor or even an intermediate or advanced user can understand>
>
> Here is what you need to do to fix that problem..... <provide the fix and explain why this fix is needed in this case>
>
> You have done nothing to educate the user and to make them more self-sufficient.
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 5:12 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Am Mon, 5 Oct 2015 21:08:02 +0000
> schrieb <Mi...@faa.gov>:
>> Answer a simple question for me, are you a Maven contributor?
>
> I fixed your stupid pom, so why would you care?
>
> Gruss
> Bernd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Here is why I care:
Well I'm not a Maven contributor. I don't wish to be. I don't even want to use the product, and wouldn't if I wasn't required to for my job.
So I get the impression that certain people answer questions because they are contributors and answer the question as if everyone else is a contributor and is expected to know the product as such.
You folks in the open source arena have a lot to learn. Your reply that you "fixed my stupid pom" is one of those things. Good customer support would go something like this.....
The problem you are having is because...... <provide an explanation here that someone who is not a contributor or even an intermediate or advanced user can understand>
Here is what you need to do to fix that problem..... <provide the fix and explain why this fix is needed in this case>
You have done nothing to educate the user and to make them more self-sufficient.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:12 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Am Mon, 5 Oct 2015 21:08:02 +0000
schrieb <Mi...@faa.gov>:
> Answer a simple question for me, are you a Maven contributor?
I fixed your stupid pom, so why would you care?
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Doug Douglass <do...@gmail.com>.
.
On Mon, Oct 5, 2015 at 2:28 PM, <Mi...@faa.gov> wrote:
> Now who has a tone?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 5:12 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Am Mon, 5 Oct 2015 21:08:02 +0000
> schrieb <Mi...@faa.gov>:
> > Answer a simple question for me, are you a Maven contributor?
>
> I fixed your stupid pom, so why would you care?
>
> Gruss
> Bernd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Now who has a tone?
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:12 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Am Mon, 5 Oct 2015 21:08:02 +0000
schrieb <Mi...@faa.gov>:
> Answer a simple question for me, are you a Maven contributor?
I fixed your stupid pom, so why would you care?
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Am Mon, 5 Oct 2015 21:08:02 +0000
schrieb <Mi...@faa.gov>:
> Answer a simple question for me, are you a Maven contributor?
I fixed your stupid pom, so why would you care?
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
My tone is the way it is because I would like a straight answer, not Maven speak.
Thank you for noticing the password. It's the only thing I've understood thus far.
Answer a simple question for me, are you a Maven contributor?
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:02 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Hello,
it is not very pleasant to help you with that kind of tone, and its rather strange that redhat refers paying customers to oss projects to fix up their projects...
Anyway, the super pom downloads a lot of stuff because your dependencies declare transitive dependencies and maven is designed to provide them all to the build project.
So it goes down all depedend POM and meta-data files, and might fail before it even starts your dependency:copy plugin.
You can stop it doing so by using a wildcard exclusion on each
dependency:
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
With that the build works for me:
203819 [INFO] BUILD SUCCESS
203821 [INFO] -------------------------------------------
203823 [INFO] Total time: 03:19 min
203825 [INFO] Finished at: 2015-10-05T22:58:39+02:00
204671 [INFO] Final Memory: 14M/120M
>tree /f target
├───apache-activemq
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.md5
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.sha1
│ apache-activemq-5.11.0.redhat-620133-bin.zip
│ apache-activemq-5.11.0.redhat-620133-bin.zip.md5
│ apache-activemq-5.11.0.redhat-620133-bin.zip.sha1
│
├───apache-camel
│ apache-camel-2.15.1.redhat-620133-src.zip
│ apache-camel-2.15.1.redhat-620133-src.zip.md5
│ apache-camel-2.15.1.redhat-620133-src.zip.sha1
│
└───apache-cxf
apache-cxf-3.0.4.redhat-620133-src.tar.gz
apache-cxf-3.0.4.redhat-620133-src.tar.gz.md5
apache-cxf-3.0.4.redhat-620133-src.tar.gz.sha1
apache-cxf-3.0.4.redhat-620133-src.zip
apache-cxf-3.0.4.redhat-620133-src.zip.md5
apache-cxf-3.0.4.redhat-620133-src.zip.sha1
BTW: your settings.xml contains a password.
Gruss
Bernd
Am Mon, 5 Oct 2015 20:18:35 +0000
schrieb <Mi...@faa.gov>:
> What do you mean by a consistent repository and POM model?
>
> If you mean that the POM must be declaring files to copy that are in
> the repository, that is stating the obvious.
>
> And in this case, the POM is doing exactly that. The files I am
> asking to be copied from the repository are actually in the
> repository. The problem is that I am getting errors for files I did
> not ask to be copied.
>
> Did you look at the POM file I attached and compare it to the error
> messages also attached?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 4:10 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Hello,
>
> I am saying that copy-dependencies is a often used method to download
> some or all dependencies of a projects. It depends on a consistent
> repository and POM model.
>
> So it is not "only a copy which does not look at the content" as you
> started, and therefore the "it is clearly a plugin or maven problem"
> might not be true.
>
> Gruss
> Bernd
>
>
> Am Mon, 5 Oct 2015 15:09:49 +0000 schrieb
> <Mi...@faa.gov>:
>
> > So, the original author of this POM may not have used the correct
> > goal to achieve the desired outcome.
> >
> > Is that in effect what you are saying?
> >
> > Michael Tarullo
> > Contractor (Engility Corp)
> > Enterprise Architect
> > NSRR System Administrator
> > FAA WJH Technical Center
> > (609)485-5294
> >
> >
> > -----Original Message-----
> > From: Bernd [mailto:ecki@zusammenkunft.net]
> > Sent: Monday, October 05, 2015 11:07 AM
> > To: Maven Users List
> > Subject: Re: Copy-dependencies goal error
> >
> > Copy Dependencies is not a simple file copy operation, it has to
> > resolve dependencies, which by definition has to look at meta data
> > and POMs. If you want to use a simple file copy a url download would
> > be easier I guess :)
> >
> > 2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
> >
> > > 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > ------------------------------------------------------------------
> > > --
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Are you a Maven contributor?
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:26 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Am Mon, 5 Oct 2015 21:20:20 +0000
schrieb <Mi...@faa.gov>:
> Could you explain why I would need to do add exclusions?
In order to stop maven from resolving all dependencies transitive until it hits a broken one.
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Am Mon, 5 Oct 2015 21:20:20 +0000
schrieb <Mi...@faa.gov>:
> Could you explain why I would need to do add exclusions?
In order to stop maven from resolving all dependencies transitive until
it hits a broken one.
Gruss
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Could you explain why I would need to do add exclusions?
If I download the ActiveMQ and CXF files without the Camel files the POM works file.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 5:02 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Hello,
it is not very pleasant to help you with that kind of tone, and its rather strange that redhat refers paying customers to oss projects to fix up their projects...
Anyway, the super pom downloads a lot of stuff because your dependencies declare transitive dependencies and maven is designed to provide them all to the build project.
So it goes down all depedend POM and meta-data files, and might fail before it even starts your dependency:copy plugin.
You can stop it doing so by using a wildcard exclusion on each
dependency:
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
With that the build works for me:
203819 [INFO] BUILD SUCCESS
203821 [INFO] -------------------------------------------
203823 [INFO] Total time: 03:19 min
203825 [INFO] Finished at: 2015-10-05T22:58:39+02:00
204671 [INFO] Final Memory: 14M/120M
>tree /f target
├───apache-activemq
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.md5
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.sha1
│ apache-activemq-5.11.0.redhat-620133-bin.zip
│ apache-activemq-5.11.0.redhat-620133-bin.zip.md5
│ apache-activemq-5.11.0.redhat-620133-bin.zip.sha1
│
├───apache-camel
│ apache-camel-2.15.1.redhat-620133-src.zip
│ apache-camel-2.15.1.redhat-620133-src.zip.md5
│ apache-camel-2.15.1.redhat-620133-src.zip.sha1
│
└───apache-cxf
apache-cxf-3.0.4.redhat-620133-src.tar.gz
apache-cxf-3.0.4.redhat-620133-src.tar.gz.md5
apache-cxf-3.0.4.redhat-620133-src.tar.gz.sha1
apache-cxf-3.0.4.redhat-620133-src.zip
apache-cxf-3.0.4.redhat-620133-src.zip.md5
apache-cxf-3.0.4.redhat-620133-src.zip.sha1
BTW: your settings.xml contains a password.
Gruss
Bernd
Am Mon, 5 Oct 2015 20:18:35 +0000
schrieb <Mi...@faa.gov>:
> What do you mean by a consistent repository and POM model?
>
> If you mean that the POM must be declaring files to copy that are in
> the repository, that is stating the obvious.
>
> And in this case, the POM is doing exactly that. The files I am
> asking to be copied from the repository are actually in the
> repository. The problem is that I am getting errors for files I did
> not ask to be copied.
>
> Did you look at the POM file I attached and compare it to the error
> messages also attached?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 4:10 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Hello,
>
> I am saying that copy-dependencies is a often used method to download
> some or all dependencies of a projects. It depends on a consistent
> repository and POM model.
>
> So it is not "only a copy which does not look at the content" as you
> started, and therefore the "it is clearly a plugin or maven problem"
> might not be true.
>
> Gruss
> Bernd
>
>
> Am Mon, 5 Oct 2015 15:09:49 +0000 schrieb
> <Mi...@faa.gov>:
>
> > So, the original author of this POM may not have used the correct
> > goal to achieve the desired outcome.
> >
> > Is that in effect what you are saying?
> >
> > Michael Tarullo
> > Contractor (Engility Corp)
> > Enterprise Architect
> > NSRR System Administrator
> > FAA WJH Technical Center
> > (609)485-5294
> >
> >
> > -----Original Message-----
> > From: Bernd [mailto:ecki@zusammenkunft.net]
> > Sent: Monday, October 05, 2015 11:07 AM
> > To: Maven Users List
> > Subject: Re: Copy-dependencies goal error
> >
> > Copy Dependencies is not a simple file copy operation, it has to
> > resolve dependencies, which by definition has to look at meta data
> > and POMs. If you want to use a simple file copy a url download would
> > be easier I guess :)
> >
> > 2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
> >
> > > 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > ------------------------------------------------------------------
> > > --
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello,
it is not very pleasant to help you with that kind of tone, and
its rather strange that redhat refers paying customers to oss
projects to fix up their projects...
Anyway, the super pom downloads a lot of stuff because your
dependencies declare transitive dependencies and maven is designed to
provide them all to the build project.
So it goes down all depedend POM and meta-data files, and might fail
before it even starts your dependency:copy plugin.
You can stop it doing so by using a wildcard exclusion on each
dependency:
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
With that the build works for me:
203819 [INFO] BUILD SUCCESS
203821 [INFO] -------------------------------------------
203823 [INFO] Total time: 03:19 min
203825 [INFO] Finished at: 2015-10-05T22:58:39+02:00
204671 [INFO] Final Memory: 14M/120M
>tree /f target
├───apache-activemq
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.md5
│ apache-activemq-5.11.0.redhat-620133-bin.tar.gz.sha1
│ apache-activemq-5.11.0.redhat-620133-bin.zip
│ apache-activemq-5.11.0.redhat-620133-bin.zip.md5
│ apache-activemq-5.11.0.redhat-620133-bin.zip.sha1
│
├───apache-camel
│ apache-camel-2.15.1.redhat-620133-src.zip
│ apache-camel-2.15.1.redhat-620133-src.zip.md5
│ apache-camel-2.15.1.redhat-620133-src.zip.sha1
│
└───apache-cxf
apache-cxf-3.0.4.redhat-620133-src.tar.gz
apache-cxf-3.0.4.redhat-620133-src.tar.gz.md5
apache-cxf-3.0.4.redhat-620133-src.tar.gz.sha1
apache-cxf-3.0.4.redhat-620133-src.zip
apache-cxf-3.0.4.redhat-620133-src.zip.md5
apache-cxf-3.0.4.redhat-620133-src.zip.sha1
BTW: your settings.xml contains a password.
Gruss
Bernd
Am Mon, 5 Oct 2015 20:18:35 +0000
schrieb <Mi...@faa.gov>:
> What do you mean by a consistent repository and POM model?
>
> If you mean that the POM must be declaring files to copy that are in
> the repository, that is stating the obvious.
>
> And in this case, the POM is doing exactly that. The files I am
> asking to be copied from the repository are actually in the
> repository. The problem is that I am getting errors for files I did
> not ask to be copied.
>
> Did you look at the POM file I attached and compare it to the error
> messages also attached?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
> -----Original Message-----
> From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 4:10 PM
> To: users@maven.apache.org
> Subject: Re: Copy-dependencies goal error
>
> Hello,
>
> I am saying that copy-dependencies is a often used method to download
> some or all dependencies of a projects. It depends on a consistent
> repository and POM model.
>
> So it is not "only a copy which does not look at the content" as you
> started, and therefore the "it is clearly a plugin or maven problem"
> might not be true.
>
> Gruss
> Bernd
>
>
> Am Mon, 5 Oct 2015 15:09:49 +0000 schrieb
> <Mi...@faa.gov>:
>
> > So, the original author of this POM may not have used the correct
> > goal to achieve the desired outcome.
> >
> > Is that in effect what you are saying?
> >
> > Michael Tarullo
> > Contractor (Engility Corp)
> > Enterprise Architect
> > NSRR System Administrator
> > FAA WJH Technical Center
> > (609)485-5294
> >
> >
> > -----Original Message-----
> > From: Bernd [mailto:ecki@zusammenkunft.net]
> > Sent: Monday, October 05, 2015 11:07 AM
> > To: Maven Users List
> > Subject: Re: Copy-dependencies goal error
> >
> > Copy Dependencies is not a simple file copy operation, it has to
> > resolve dependencies, which by definition has to look at meta data
> > and POMs. If you want to use a simple file copy a url download
> > would be easier I guess :)
> >
> > 2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
> >
> > > 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
What do you mean by a consistent repository and POM model?
If you mean that the POM must be declaring files to copy that are in the repository, that is stating the obvious.
And in this case, the POM is doing exactly that. The files I am asking to be copied from the repository are actually in the repository. The problem is that I am getting errors for files I did not ask to be copied.
Did you look at the POM file I attached and compare it to the error messages also attached?
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd Eckenfels [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 4:10 PM
To: users@maven.apache.org
Subject: Re: Copy-dependencies goal error
Hello,
I am saying that copy-dependencies is a often used method to download some or all dependencies of a projects. It depends on a consistent repository and POM model.
So it is not "only a copy which does not look at the content" as you started, and therefore the "it is clearly a plugin or maven problem"
might not be true.
Gruss
Bernd
Am Mon, 5 Oct 2015 15:09:49 +0000 schrieb
<Mi...@faa.gov>:
> So, the original author of this POM may not have used the correct goal
> to achieve the desired outcome.
>
> Is that in effect what you are saying?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Bernd [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 11:07 AM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Copy Dependencies is not a simple file copy operation, it has to
> resolve dependencies, which by definition has to look at meta data and
> POMs. If you want to use a simple file copy a url download would be
> easier I guess :)
>
> 2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
>
> > 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello,
I am saying that copy-dependencies is a often used method to download
some or all dependencies of a projects. It depends on a consistent
repository and POM model.
So it is not "only a copy which does not look at the content" as you
started, and therefore the "it is clearly a plugin or maven problem"
might not be true.
Gruss
Bernd
Am Mon, 5 Oct 2015 15:09:49 +0000 schrieb
<Mi...@faa.gov>:
> So, the original author of this POM may not have used the correct
> goal to achieve the desired outcome.
>
> Is that in effect what you are saying?
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Bernd [mailto:ecki@zusammenkunft.net]
> Sent: Monday, October 05, 2015 11:07 AM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Copy Dependencies is not a simple file copy operation, it has to
> resolve dependencies, which by definition has to look at meta data
> and POMs. If you want to use a simple file copy a url download would
> be easier I guess :)
>
> 2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
>
> > 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
So, the original author of this POM may not have used the correct goal to achieve the desired outcome.
Is that in effect what you are saying?
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Bernd [mailto:ecki@zusammenkunft.net]
Sent: Monday, October 05, 2015 11:07 AM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Copy Dependencies is not a simple file copy operation, it has to resolve dependencies, which by definition has to look at meta data and POMs. If you want to use a simple file copy a url download would be easier I guess :)
2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
> 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Copy-dependencies goal error
Posted by Bernd <ec...@zusammenkunft.net>.
Copy Dependencies is not a simple file copy operation, it has to resolve
dependencies, which by definition has to look at meta data and POMs. If you
want to use a simple file copy a url download would be easier I guess :)
2015-10-05 16:34 GMT+02:00 <Mi...@faa.gov>:
> 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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
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:waynefay@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, <Mi...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Wayne Fay <wa...@gmail.com>.
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, <Mi...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
That is exactly what I would like to know!!!
Mike
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
Sent: Monday, October 05, 2015 12:43 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Hi,
On 10/5/15 6:07 PM, Jörg Schaible wrote:
> latest Maven version or 3.0.5,
> because 3.1.1. is bogus.
Can you tell me in which way 3.1.1 is bogus ?
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
On 10/5/15 6:07 PM, Jörg Schaible wrote:
> latest Maven version or 3.0.5,
> because 3.1.1. is bogus.
Can you tell me in which way 3.1.1 is bogus ?
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
To anyone following this absolutely frustrating thread, neither v3.0.5 nor v3.3.3 solved this problem. V3.3.3 resulted in the same error and v3.0.5 failed with a different error!!!
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.schaible@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.Tarullo@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Thank you Curtis.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: ctrueden.wisc@gmail.com [mailto:ctrueden.wisc@gmail.com] On Behalf Of Curtis Rueden
Sent: Monday, October 05, 2015 2:36 PM
To: Maven Users List
Cc: joerg.schaible@gmx.de
Subject: Re: Copy-dependencies goal error
Hi Michael,
> Can you explain " you are using dependencyManagement with dependencies
> declared with scope "import""?
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
> I don't see anything in either my settings.xml or pom.xml that
> explicitly declares this.
Agreed -- I don't see any uses of import scope in the POM attachment you sent.
Regards,
Curtis
On Mon, Oct 5, 2015 at 1:21 PM, <Mi...@faa.gov> wrote:
> What is "import scope"?
>
> I don't see anything in either my settings.xml or pom.xml that
> explicitly declares this. (And I call this my POM, but I inherited it
> from someone else).
>
> Can you explain " you are using dependencyManagement with dependencies
> declared with scope "import""?
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 1:51 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
> > My apology about part of this reply. I did not understand part of
> > your suggestion.
> >
> > I thought you were saying 3.0.5 is the latest release.
> >
> > That said, I don't see how using the latest release or an older
> > release makes any difference.
> >
> > I have a requirement to use 3.1.1 from a COTS product vendor, so
> > that is probably not an option. And "bogus" is just not a good
> > enough explanation for me. What specifically is wrong with what I
> > am doing that does not work in this release?
>
> I just cite my original mail:
>
> > IIRC you have problems with 3.1.x when using dependencies with
> > import scope, because it ignores then your settings then for
> > transitive deps declaring their own repository in the POM.
>
> AFAICS, you are using dependencyManagement with dependencies declared
> with scope "import"".
>
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Copy-dependencies goal error
Posted by Curtis Rueden <ct...@wisc.edu>.
Hi Michael,
> Can you explain " you are using dependencyManagement with dependencies
> declared with scope "import""?
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
> I don't see anything in either my settings.xml or pom.xml that
> explicitly declares this.
Agreed -- I don't see any uses of import scope in the POM attachment you
sent.
Regards,
Curtis
On Mon, Oct 5, 2015 at 1:21 PM, <Mi...@faa.gov> wrote:
> What is "import scope"?
>
> I don't see anything in either my settings.xml or pom.xml that explicitly
> declares this. (And I call this my POM, but I inherited it from someone
> else).
>
> Can you explain " you are using dependencyManagement with dependencies
> declared with scope "import""?
>
> 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.schaible@gmx.de]
> Sent: Monday, October 05, 2015 1:51 PM
> To: users@maven.apache.org
> Subject: RE: Copy-dependencies goal error
>
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
> > My apology about part of this reply. I did not understand part of
> > your suggestion.
> >
> > I thought you were saying 3.0.5 is the latest release.
> >
> > That said, I don't see how using the latest release or an older
> > release makes any difference.
> >
> > I have a requirement to use 3.1.1 from a COTS product vendor, so that
> > is probably not an option. And "bogus" is just not a good enough
> > explanation for me. What specifically is wrong with what I am doing
> > that does not work in this release?
>
> I just cite my original mail:
>
> > IIRC you have problems with 3.1.x when using dependencies with import
> > scope, because it ignores then your settings then for transitive deps
> > declaring their own repository in the POM.
>
> AFAICS, you are using dependencyManagement with dependencies declared with
> scope "import"".
>
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
What is "import scope"?
I don't see anything in either my settings.xml or pom.xml that explicitly declares this. (And I call this my POM, but I inherited it from someone else).
Can you explain " you are using dependencyManagement with dependencies declared with scope "import""?
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.schaible@gmx.de]
Sent: Monday, October 05, 2015 1:51 PM
To: users@maven.apache.org
Subject: RE: Copy-dependencies goal error
Hi Michael,
Michael.CTR.Tarullo@faa.gov wrote:
> My apology about part of this reply. I did not understand part of
> your suggestion.
>
> I thought you were saying 3.0.5 is the latest release.
>
> That said, I don't see how using the latest release or an older
> release makes any difference.
>
> I have a requirement to use 3.1.1 from a COTS product vendor, so that
> is probably not an option. And "bogus" is just not a good enough
> explanation for me. What specifically is wrong with what I am doing
> that does not work in this release?
I just cite my original mail:
> IIRC you have problems with 3.1.x when using dependencies with import
> scope, because it ignores then your settings then for transitive deps
> declaring their own repository in the POM.
AFAICS, you are using dependencyManagement with dependencies declared with scope "import"".
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Thank you Karl.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
Sent: Monday, October 05, 2015 6:22 PM
To: Maven Users List; info@soebes.de
Subject: Re: Copy-dependencies goal error
Hi Michael,
I'm replying to Jörg...
Kind regards
Karl Heinz Marbaise
On 10/6/15 12:14 AM, Michael.CTR.Tarullo@faa.gov wrote:
> Karl,
>
> Could you clarify this. I don't understand your reply.
>
> In fact I'm not sure if you are replying to me or Jorg.
>
> It appears to be the latter. Could you please confirm?
>
> Thank you.
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> Sent: Monday, October 05, 2015 6:10 PM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Hi,
>
> On 10/5/15 7:51 PM, Jörg Schaible wrote:
>> Hi Michael,
>>
>> Michael.CTR.Tarullo@faa.gov wrote:
>>
>>> My apology about part of this reply. I did not understand part of
>>> your suggestion.
>>>
>>> I thought you were saying 3.0.5 is the latest release.
>>>
>>> That said, I don't see how using the latest release or an older
>>> release makes any difference.
>>>
>>> I have a requirement to use 3.1.1 from a COTS product vendor, so
>>> that is probably not an option. And "bogus" is just not a good
>>> enough explanation for me. What specifically is wrong with what I
>>> am doing that does not work in this release?
>>
>> I just cite my original mail:
>>
>>> IIRC you have problems with 3.1.x when using dependencies with
>>> import scope, because it ignores then your settings then for
>>> transitive deps declaring their own repository in the POM.
>>
>> AFAICS, you are using dependencyManagement with dependencies declared
>> with scope "import"".
>
>
> The given pom does not contain any dependencyManagement...so it does simply plays not a role here...Apart from that import scope means only to use the dependencyManagement part and nothing else as described in the documentation...so it does not ignore it nor is it wrong...
>
> See the original documentation
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
>
> so this is NOT a problem in contrary it is exactly working as it should be...Apart from using repository definition in a pom is a bad practice...But this is a different story...
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Michael,
I'm replying to Jörg...
Kind regards
Karl Heinz Marbaise
On 10/6/15 12:14 AM, Michael.CTR.Tarullo@faa.gov wrote:
> Karl,
>
> Could you clarify this. I don't understand your reply.
>
> In fact I'm not sure if you are replying to me or Jorg.
>
> It appears to be the latter. Could you please confirm?
>
> Thank you.
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> Sent: Monday, October 05, 2015 6:10 PM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Hi,
>
> On 10/5/15 7:51 PM, Jörg Schaible wrote:
>> Hi Michael,
>>
>> Michael.CTR.Tarullo@faa.gov wrote:
>>
>>> My apology about part of this reply. I did not understand part of
>>> your suggestion.
>>>
>>> I thought you were saying 3.0.5 is the latest release.
>>>
>>> That said, I don't see how using the latest release or an older
>>> release makes any difference.
>>>
>>> I have a requirement to use 3.1.1 from a COTS product vendor, so that
>>> is probably not an option. And "bogus" is just not a good enough
>>> explanation for me. What specifically is wrong with what I am doing
>>> that does not work in this release?
>>
>> I just cite my original mail:
>>
>>> IIRC you have problems with 3.1.x when using dependencies with import
>>> scope, because it ignores then your settings then for transitive deps
>>> declaring their own repository in the POM.
>>
>> AFAICS, you are using dependencyManagement with dependencies declared
>> with scope "import"".
>
>
> The given pom does not contain any dependencyManagement...so it does simply plays not a role here...Apart from that import scope means only to use the dependencyManagement part and nothing else as described in the documentation...so it does not ignore it nor is it wrong...
>
> See the original documentation
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
>
> so this is NOT a problem in contrary it is exactly working as it should be...Apart from using repository definition in a pom is a bad practice...But this is a different story...
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
Karl,
Could you clarify this. I don't understand your reply.
In fact I'm not sure if you are replying to me or Jorg.
It appears to be the latter. Could you please confirm?
Thank you.
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
Sent: Monday, October 05, 2015 6:10 PM
To: Maven Users List
Subject: Re: Copy-dependencies goal error
Hi,
On 10/5/15 7:51 PM, Jörg Schaible wrote:
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
>> My apology about part of this reply. I did not understand part of
>> your suggestion.
>>
>> I thought you were saying 3.0.5 is the latest release.
>>
>> That said, I don't see how using the latest release or an older
>> release makes any difference.
>>
>> I have a requirement to use 3.1.1 from a COTS product vendor, so that
>> is probably not an option. And "bogus" is just not a good enough
>> explanation for me. What specifically is wrong with what I am doing
>> that does not work in this release?
>
> I just cite my original mail:
>
>> IIRC you have problems with 3.1.x when using dependencies with import
>> scope, because it ignores then your settings then for transitive deps
>> declaring their own repository in the POM.
>
> AFAICS, you are using dependencyManagement with dependencies declared
> with scope "import"".
The given pom does not contain any dependencyManagement...so it does simply plays not a role here...Apart from that import scope means only to use the dependencyManagement part and nothing else as described in the documentation...so it does not ignore it nor is it wrong...
See the original documentation
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
so this is NOT a problem in contrary it is exactly working as it should be...Apart from using repository definition in a pom is a bad practice...But this is a different story...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@swisspost.com>.
Karl Heinz Marbaise wrote:
> Hi,
>
> On 10/5/15 7:51 PM, Jörg Schaible wrote:
>> Hi Michael,
>>
>> Michael.CTR.Tarullo@faa.gov wrote:
>>
>>> My apology about part of this reply. I did not understand part of your
>>> suggestion.
>>>
>>> I thought you were saying 3.0.5 is the latest release.
>>>
>>> That said, I don't see how using the latest release or an older release
>>> makes any difference.
>>>
>>> I have a requirement to use 3.1.1 from a COTS product vendor, so that is
>>> probably not an option. And "bogus" is just not a good enough
>>> explanation
>>> for me. What specifically is wrong with what I am doing that does not
>>> work in this release?
>>
>> I just cite my original mail:
>>
>>> IIRC you have problems with 3.1.x when using dependencies with import
>>> scope, because it ignores then your settings then for transitive
>>> deps declaring their own repository in the POM.
>>
>> AFAICS, you are using dependencyManagement with dependencies declared
>> with scope "import"".
>
>
> The given pom does not contain any dependencyManagement...so it does
> simply plays not a role here...
If you read the OPs question from last week, you will see that he did not
provide his POM there and from that description, I assumed he used an import
scope. That was not the case.
> Apart from that import scope means only
> to use the dependencyManagement part and nothing else as described in
> the documentation...so it does not ignore it nor is it wrong...
And what does that have to do with the stuff defined in settings.xml?
> See the original documentation
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
As long as the dependencies are resolved from the repos declared in
settings.xml ...
https://issues.apache.org/jira/browse/MNG-5781
We were affected by this more than once, but - honestly - I could not
reproduce it today (3.3.3, 3.1.1, 3.0.5).
> so this is NOT a problem in contrary it is exactly working as it should
> be...Apart from using repository definition in a pom is a bad
> practice...
Definitely.
> But this is a different story...
Sadly it was not forbidden when it was discussed the last time ...
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
On 10/5/15 7:51 PM, Jörg Schaible wrote:
> Hi Michael,
>
> Michael.CTR.Tarullo@faa.gov wrote:
>
>> My apology about part of this reply. I did not understand part of your
>> suggestion.
>>
>> I thought you were saying 3.0.5 is the latest release.
>>
>> That said, I don't see how using the latest release or an older release
>> makes any difference.
>>
>> I have a requirement to use 3.1.1 from a COTS product vendor, so that is
>> probably not an option. And "bogus" is just not a good enough explanation
>> for me. What specifically is wrong with what I am doing that does not
>> work in this release?
>
> I just cite my original mail:
>
>> IIRC you have problems with 3.1.x when using dependencies with import
>> scope, because it ignores then your settings then for transitive
>> deps declaring their own repository in the POM.
>
> AFAICS, you are using dependencyManagement with dependencies declared with
> scope "import"".
The given pom does not contain any dependencyManagement...so it does
simply plays not a role here...Apart from that import scope means only
to use the dependencyManagement part and nothing else as described in
the documentation...so it does not ignore it nor is it wrong...
See the original documentation
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
so this is NOT a problem in contrary it is exactly working as it should
be...Apart from using repository definition in a pom is a bad
practice...But this is a different story...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Michael,
Michael.CTR.Tarullo@faa.gov wrote:
> My apology about part of this reply. I did not understand part of your
> suggestion.
>
> I thought you were saying 3.0.5 is the latest release.
>
> That said, I don't see how using the latest release or an older release
> makes any difference.
>
> I have a requirement to use 3.1.1 from a COTS product vendor, so that is
> probably not an option. And "bogus" is just not a good enough explanation
> for me. What specifically is wrong with what I am doing that does not
> work in this release?
I just cite my original mail:
> IIRC you have problems with 3.1.x when using dependencies with import
> scope, because it ignores then your settings then for transitive
> deps declaring their own repository in the POM.
AFAICS, you are using dependencyManagement with dependencies declared with
scope "import"".
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
My apology about part of this reply. I did not understand part of your suggestion.
I thought you were saying 3.0.5 is the latest release.
That said, I don't see how using the latest release or an older release makes any difference.
I have a requirement to use 3.1.1 from a COTS product vendor, so that is probably not an option. And "bogus" is just not a good enough explanation for me. What specifically is wrong with what I am doing that does not work in this release?
Mike
Michael Tarullo
Contractor (Engility Corp)
Enterprise Architect
NSRR System Administrator
FAA WJH Technical Center
(609)485-5294
-----Original Message-----
From: Tarullo, Michael CTR (FAA)
Sent: Monday, October 05, 2015 12:20 PM
To: users@maven.apache.org
Subject: RE: Copy-dependencies goal error
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.schaible@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.Tarullo@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Copy-dependencies goal error
Posted by Mi...@faa.gov.
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.schaible@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.Tarullo@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Copy-dependencies goal error
Posted by Jörg Schaible <jo...@swisspost.com>.
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.Tarullo@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org