@Steve Is this critical for your build, or can we postpone this to 1.0?

It is not critical for me. The alternative it to just use the 'compilerArgs' setting, which is what I do currently.

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!

Again, this is something I personally think is worthwhile. But again as mentioned on GRADLE-3291, if this is something y'all have zero interest in then please just close it and do not migrate it.

Can be implemented in a build via compilerArgs.