You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2017/04/15 20:38:41 UTC

[jira] [Updated] (MDEP-444) maven-dependency-plugin goal copy-dependencies version 2.8 with flag stripVersion=false is always overwriting files even when artifact has not changed

     [ https://issues.apache.org/jira/browse/MDEP-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MDEP-444:
--------------------------------
    Labels: close-pending  (was: )

> maven-dependency-plugin goal copy-dependencies version 2.8 with flag stripVersion=false is always overwriting files even when artifact has not changed
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MDEP-444
>                 URL: https://issues.apache.org/jira/browse/MDEP-444
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: copy-dependencies
>    Affects Versions: 2.8
>            Reporter: Andres Oviedo
>            Priority: Minor
>              Labels: close-pending
>             Fix For: more-investigation
>
>
> Issue:
> * When executing maven-dependency-plugin goal copy-dependencies version 2.8, with flag stripVersion=true, only modified 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 lastModification date for remote and local artifact, 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)