[GRADLE-3564] Gradle does not handle include files included via macro Created: 20/Sep/16 Updated: 10/Feb/17 Resolved: 10/Feb/17
When a native source file or a transitive header of a dource file does something like
And then programmatically or via command line argument sets SOMEMACRO to a file path, Gradle cannot determine the value of SOMEMACRO and cannot determine tthe complete set of inputs for the task.
In this case, Gradle will consoder any source file as out of date that includes headers in this way when _any _ for the task changes.
This can cause unexpectedly longer compilation times when the user expects only a single file to be compiled.
|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:
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.