[GRADLE-2708] Task properties are not in scope in Script copy method Created: 15/Mar/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Steinar Haugen Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Known Issue Of:


Properties defined in a task that performs copy using the Script.copy method are not in scope in the Script copy method closure.

A minor issue, but since it is in scope everywhere else inside the task, it is a bit confusing. The error message (see below) also made it more confusing.

task myCopy {
    ext.destinationDir = file("$buildDir/myCopyDir")
    doLast {
        destinationDir.mkdirs()     // here it is in scope
        copy {
            from "$rootDir/myFile.txt"
            into destinationDir     // fails: here it is no longer in scope

This fails with the message: InvalidUserDataException: No copy destination directory has been specified, use 'into' to specify a target directory.

This message just made it more confusing.

If the "into" statement is changed to:

into myCopy.destinationDir

then the copy works as expected.

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:29:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.