[GRADLE-409] There should be a task type for files that corrsponds to a Make target that isn't .PHONY (perhaps using MD5, timestamp, or some tunable function) Created: 19/Feb/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Jon Cox Assignee: Unassigned
Resolution: Won't Fix Votes: 1


The createTask(...) api in Gradle creates what amounts to a .PHONY target in Gnu Make.
That's very useful but so are non .PHONY targets, such as file names.

It would also be nice if there were a nice syntax for specifying how the dependsOn relationship
for a file target is evaluated. The two obvious methods are time stamp (like Make and most others)
and some sort of crypto hash such as MD5 or SHA1 (like Scons and Rant).

For more information on 'Rant', see: http://rant.rubyforge.org/
For more information on Scons, see: http://www.scons.org/

You could also imagine how there could be a need to plug in an arbitrary function,
so it would be great if Gradle could do that too.

The benefit of MD5 over time stamps is that it eliminates clock skew problems
(however it is more expensive to evaluate). Thus, an ideal solution would let you
do whatever you wanted globally and/or target-by-target (with the ability to override
a global default).

Obviously, a file task should be allowed to depend on both file and non-file tasks.

It might be worth starting a discussion thread on the mailing list about this
and explore the pros/cons of different syntax proposals.

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