[GRADLE-1474] ZipTask is skipped although the sources were changed by a previous task Created: 14/Apr/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Leonard Brünings Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: Zip Archive GradleZipExample.zip    

 Description   

In the attached project you can find the sample to recreate the problem.

As far as I understand it, this is caused by the different life cycle phases of gradle.
The 'from' directive is evaluated in the configuration phase where the other zip files
are not yet present causing the up-to-date check to think there are no new files.

I've included a workaround in the zip, but this includes one task manipulating the 'from'
directive of an other task and this just doesn't feel right.

What we need here is a delayed evaluation for the 'from' directive to include the output
of the previous tasks.

While testing please make sure to make a stand alone clean run before you try it again.

 Comments   
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:56:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.