[GRADLE-2898] Copy task fails, erroneously claiming it is UP-TO-DATE with Gradle 1.8 Created: 25/Sep/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 6


In code that works with Gradle 1.7 and I think 1.8-rc-1 (maybe also rc-2) I have a copy task configured like so:

task setupBaseSDK(type: Copy, dependsOn: [configurations.baseZip]) {
into stagingDir
from { configurations.baseZip.findAll

{ it.name.endsWith(".zip") }.collect { zipTree(it) } }
from { configurations.repoClientZip.findAll { it.name.endsWith(".zip") }


{ zipTree(it) }


{ into 'RepositoryClient' }


With Gradle 1.8 it claims to be UP-TO-DATE even though the destination directory is missing all of the files from the zips.

Comment by Gradle Forums [ 25/Sep/13 ]

Did you do a clean build after bumping the Gradle version? I'd be surprised if anything changed here. Also `dependsOn repoClientZip` appears to be missing.

Comment by Gradle Forums [ 25/Sep/13 ]

Yes I did do a clean build. But maybe I need to manually delete things like the .gradle folder?

Comment by Gradle Forums [ 25/Sep/13 ]

Normally it shouldn't be necessary to delete other stuff. Are you saying that a clean build now results in an "empty" copy? Maybe something's wrong with the configurations or their contents then?

Comment by Gradle Forums [ 25/Sep/13 ]

I've added the dependency and deleted my ~/.gradle folder , then I did a clean build... same problem. Works fine with 1.7.

Comment by Gradle Forums [ 25/Sep/13 ]

Fixed it.. needed to delete the .gradle folder from the parent project directory.

Comment by David Moles [ 29/May/14 ]

FWIW, I'm still seeing this with Gradle 1.11. I worked around it by adding

    outputs.upToDateWhen { false }

to my copy task.

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 12:34:26 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.