You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by Andres Oviedo <an...@gmail.com> on 2014/04/30 11:38:02 UTC

maven-dependency-plugin goal copy-dependencies version 2.8 with flag stripVersion=false is always overwriting files.

Issue:
* When executing maven-dependency-plugin goal copy-dependencies version
2.8, with flag stripVersion=true, only modifed artifacts at nexus are being
overwritten at local folder destination (that's ok! so no problem here),
 but when stripVersion=false, all files are being overwritten at
destination, even when no changes has been made to remote artifacts.

Diagnostic:
* Debugging maven-dependency-plugin i think i have seen the bug.  The class
org.apache.maven.plugin.dependency.utils.filters.DestFileFilter is ignoring
"useBaseVersion" flag.  So, when comparing for lastModification date for
remote and current artifact is made, destination file never exists because
the generated destination filename has the unique version instead the
baseVersion.

Proposed solution:
* Propagate "useBaseVersion" flag
to org.apache.maven.plugin.dependency.utils.DependencyUtil#getFormattedFileName()
method to append baseVersion instead uniqueVersion.

Best Regards,
Andrés Oviedo