maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David M. Karr" <>
Subject Why isn't maven-dependency-plugin copying my artifacts anymore?
Date Thu, 10 Mar 2016 22:31:37 GMT
Several days ago, on the advice of someone on another list, I configured 
the use of the "maven-dependency-plugin" in my POM so that the build 
would copy some dependencies into a local folder, not inside the target 

This worked the very first time I ran the build with it, and I've been 
using the results for a while.

Today I started to look at this again, to ensure that these copied 
artifacts would be properly cleaned up from "mvn clean".  I first tried 
reconfiguring where it wrote the jars, changing it from "libs" to 
"target/libs".  For some reason, when I ran the build, it didn't create 
"target/libs", nor did it copy the jars.  At that point, I thought there 
was some issue with writing them into a subfolder of "target".

I then changed it back to "libs", but I implemented additional 
"maven-clean-plugin" configuration to make it delete that folder. When I 
ran "mvn clean", it did what I expected, removing that folder, along 
with "target".

However, when I then tried to build the whole thing again, I found that 
it wasn't creating the "libs" folder, and it wasn't copying the jars 
there.  I then tried manually creating "libs", but that didn't help.  I 
tried adding "--debug", which didn't tell me anything useful.  I imagine 
the same thing that is making it not copy the jars into "libs" is the 
same thing that prevented it writing them into "target/libs", so there 
likely wasn't a real issue with using a subfolder of "target", but 
something else is just preventing it from copying the jars.

This is what I have in the POM for this plugin (eliding the details of 
each artifact):

What might be wrong here?

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

View raw message