[GRADLE-2985] Using `each` makes include global on `jar` task Created: 10/Jan/14  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: 0


 Description   

I notice the following problem in v1.10:

def someFiles = [ "some", "files" ]

jar {
into("subdir") {
from(project.projectDir) {
someFiles.each

{ include it }

}
}
}

This results in the files being added to the `subdir` in the created jar file. However, they are the only files added to the jar file! I would have expected that these are added additionally to the jar file besides the normal project output.

The following gives the desired effect:

jar {
into("subdir") {
from(project.projectDir) {
include someFiles
}
}
}

Is this a misunderstanding on my side how this should work? Or is it a bug?



 Comments   
Comment by Gradle Forums [ 10/Jan/14 ]

Your syntax is unconventional, and I'm not sure if and how it is supposed to work. Have you only had this problem since 1.10? Does the following solve it?

def someFiles = [ "some", "files" ]
jar {
into("subdir") {
from(project.projectDir)
someFiles.each

{ include it }

}
}

Comment by Gradle Forums [ 10/Jan/14 ]

Oh. Ok. I thought I saw this in an example somewhere, but I might be mistaken. I would have expected that something like the following is a reasonable thing to do.

jar {
into("subdir") {
from("a") {
include "some-a-file"
}
from("b") {
include "some-b-file"
}
}
}

Edit: I only tested with v1.10. That's what I'm currently running.

Comment by Gradle Forums [ 10/Jan/14 ]

To a certain degree, this expectation doesn't seem to be too far off since it actually works. However, the `each` + closure makes things go nuts, which is a bit surprising given the fact that the plain include works.

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