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) @ > com.cisco.yangide.core --- > [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/com.cisco.yangide.core/target/classes 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. Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
