[GRADLE-1264] Cannot always overwrite files with Copy task (it uses "overwrite if newer" strategy) Created: 21/Dec/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: Hendy Irawan Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Copy task overwrites files if the source is newer.

There must be a way of specifying an alternate strateg(ies):

  • always overwrite files (this is most important)
  • only update existing files with newer versions, but ignore non-existing ones
  • only copy new files, leave existing files alone (i.e. never overwrite)
  • copy if newer or size different

Ant's Copy task can do this, Gradle's own Copy task should be able to do it too.

 Comments   
Comment by Adam Murdoch [ 04/Jan/11 ]

As of Gradle 0.9.1, the Copy task always overwrites files. The other strategies are not supported yet.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:51:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.