maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David M. Karr" <>
Subject Re: Why isn't maven-dependency-plugin copying my artifacts anymore?
Date Fri, 11 Mar 2016 16:50:49 GMT
On 03/11/2016 08:40 AM, Jörg Schaible wrote:
> David M. Karr wrote:
>> On 03/10/2016 09:43 PM, Uwe Barthel wrote:
>>> I tried:
>>> 'mvn clean' removes the lib/ and target/ folder.
>>> 'mvn package' puts the libs into lib/ again.
>>> I delete all libs in lib/ folder but let the lib/ folder itself and the
>>> target folder untouched. ‘mvn package’ works as expected.
>> As usual, this still isn't doing anything for me.
>> This time I looked closer at the console output.  I'm thinking there's a
>> clue here.  I looked closer at the output from
>> "maven-dependency-plugin".  This is what I saw:
>> -------------------------
>> [INFO] --- maven-dependency-plugin:2.10:unpack (unpack-license) @
>> ---
>> [INFO] Configured Artifact:
>> org.opendaylight.odlparent:odl-license:0.0.1-SNAPSHOT:jar
>> [INFO] Unpacking
>> .../.m2/repository/org/opendaylight/odlparent/odl-license/0.0.1-
> SNAPSHOT/odl-license-0.0.1-SNAPSHOT.jar
>> to .../git/yangide/plugins/ with
>> includes "" and excludes "META-INF/**"
>> -----------------------
>> This is the only occurrence of "maven-dependency-plugin" in the build
>> output, and notice that it's the "unpack" goal, not the "copy" goal.
>> This reference to the "unpack" goal is in the parent of the parent of
>> this pom.  Is this causing the maven-dependency-plugin to somehow skip
>> the "copy" goal?
> Use "mvn help:effective-pom" to see what Maven actually uses after merging
> the POM with the parent.

Yeah, I started working with that already, and commenting out portions 
until I get different behavior, which hasn't happened yet. The reference 
to the other maven-dependency-plugin goal appears to be irrelevant.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message