[GRADLE-2025] zipTree(someTask) does not carry dependency information Created: 04/Jan/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6
Fix Version/s: None

Type: Bug
Reporter: Luke Daley Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Something like the following should work

apply plugin: "java"
task someJar(type: Jar) {
   from zipTree(jar)

However, you need to do this:

apply plugin: "java"
task someJar(type: Jar, dependsOn: jar) {
   from zipTree(jar)

When a zipTree is constructed from a buildable, it should inherit it.

Comment by Chris Beams [ 04/Jan/12 ]

In the actual use case from which this issue arose, I'm building up a distribution zip by depending on and unpacking other smaller zips, e.g.:

task distZip(type: Zip, dependsOn: docsZip) {
    from zipTree(docsZip)

The expected behavior would be that I can omit the dependsOn declaration, and that the task dependency would be implicit:

task distZip(type: Zip) {
    from zipTree(docsZip)

Note that I don't think this has anything directly to do with zipTree; even the following doesn't work as expected (i.e. still requires the explicit dependsOn)

task distZip(type: Zip) {
    from docsZip // will silently fail without an explicit 'dependsOn: docsZip'!

This problem seems only to happen for Zip tasks, and not for Jar tasks, for example, the following snippet taken from that same distZip task works fine:

  subprojects.each { subproject ->
        into("${baseDir}/libs") {
            from subproject.jar
            from subproject.sourcesJar
            from subproject.javadocJar

and nowhere in that task definition do I say dependsOn subproject.jar, etc.

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