Maven dependancy unpack

[David Gibson]

I have a assembly that I unpack over the target of another project. If there are duplicate files then I don't want the unpack to overwrite the file in question. I would have thought setting <overWrite>false</overWrite> would have prevented this, but it doesn't seem the case.

This is the configuration I am using, any help would be appreciated

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>unpack</id>
<phase>compile</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>test.test</groupId>
<artifactId>base</artifactId>
<version>2.4.0-SNAPSHOT</version>
<classifier>war-fragment</classifier>
<outputDirectory>target/${project.build.finalName}</outputDirectory>
<overWrite>false</overWrite>
</artifactItem>
</artifactItems>
<overWriteIfNewer>false</overWriteIfNewer>
</configuration>
</execution>
</executions>
</plugin>

[Martijn Verburg]

Is the dependency plugin the right one to use in this case?

[David Gibson]

I have a dependency and I need to unpack the contents into a directory that contains other files. If a file exists in the directory and also exists in the dependency then I want the directory version. Having spent a long time browsing the internet to find a solution, this gave me the nearest result. I would have thought that my requirement of unpacking a dependency but not overwriting existing files would be fulfilled by maven-dependency-plugin:unpack with the overWrite config set to false, but I must be mistaken. If you know of an alternative way then please let me know, I am all ears

[Martijn Verburg]

Are you specifying the latest dependency plugin?

[David Gibson]

We are using Maven Dependency Plugin 2.1

[Martijn Verburg]

Only thing I can suggest is to check their JIRA and/or raise the bug on their mailing list.