[
http://jira.codehaus.org/browse/MDEP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205631#action_205631
]
Brian Fox commented on MDEP-154:
--------------------------------
what do you mean by global updatePolicy?
> 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: [email protected] [mailto:[email protected]]
> Sent: Wednesday, March 05, 2008 7:00 AM
> To: [email protected]
> 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
