You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Philippe Bourgau (JIRA)" <ji...@codehaus.org> on 2010/01/07 18:02:55 UTC

[jira] Commented: (MDEP-154) dependency:copy always creates new timestamp, when copying from Repository to local filesystem

    [ http://jira.codehaus.org/browse/MDEP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205577#action_205577 ] 

Philippe Bourgau commented on MDEP-154:
---------------------------------------

Hi,

We are having exactly the same issue with unpack-dependencies. The consequence is that dependencies get unpacked once again, even if they did not change. This slows the build down, and as we are using unpack-dependencies for our dev builds, it is really annoying.

How to reproduce:
It is easier to reproduce the problem with the global updatePolicy option set to always. Suppose that the dependencies did not change in your global repository. When running unpack-dependencies:

 1 - in your local repository the dependencies get a new timestamp (strange, no real download, it's just a touch)
 2 - the metadata for the dependencies in the local repo do not change
 3 - the dependencies are unpacked for nothing
 4 - the markers for the unpack-dependencies are not updated (this seems weird according to point 3)

Thank you,

Philippe

> dependency:copy always creates new timestamp, when copying from Repository to local filesystem
> ----------------------------------------------------------------------------------------------
>
>                 Key: MDEP-154
>                 URL: http://jira.codehaus.org/browse/MDEP-154
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>          Components: copy, copy-dependencies
>    Affects Versions: 2.1
>         Environment: Windows XP
> <version>2.0-alpha-5-20080115.230021-25</version>
>            Reporter: Torsten Reinhard
>            Assignee: Brian Fox
>            Priority: Minor
>
> From: torsten.reinhard@gi-de.com [mailto:torsten.reinhard@gi-de.com] 
> Sent: Wednesday, March 05, 2008 7:00 AM
> To: users@maven.apache.org
> Subject: dependency:copy always creates new timestamp
> Hi, 
> to create the delivery version of our whole system, I use 
> "dependency:copy" and "dependency:copy-dependencies" 
> to copy the jars, ears, wars and so on from our internal repository into a 
> defined directory structure.
> <productVersion>
>         Install
>                 Module-A
>                         xyz.war
>                 Module-B
>                         xyz.ear
>         Documentation
>                 *.doc
> Every time I start the "delivery build", the copied artifacts get new 
> timestamps - although the version hasn´t changed in between.
> I couldn´t find any property "keep original timestamp" to set for the 
> goals "copy" or "copy-dependencies".
> Is there a way?
> Thanx, Torsten

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira