[GRADLE-1693] Tooling API should provide informatin about which Groovy compiler (version) should be used for parsing build.gradle Created: 26/Jul/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Kris De Volder||Assignee:||Unassigned|
Editor support for build.gradle will need to know which parser to use for the build.gradle file.
Note (FYI): Greclipse can't at the moment support more than one Groovy compiler in the same Eclipse instance. However, in the long run we hope to resolve this somehow. Also even if it is impossible to switch the compiler dynamically, it is better to detect that an incompatible version is being used than to simply produce cryptic errors and weird behavior in the editor because of syntactic differences between (say for example) Groovy 1.8 and Groovy 1.7.
|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.