[GRADLE-1538] Tooling API should provide information on Groovy nature and version Created: 12/May/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Kris De Volder||Assignee:||Unassigned|
So that Eclipse knows when a project should be configured as Groovy project and which compiler it should use (Groovy 1.8 versus Groovy 1.7).
|Comment by Kris De Volder [ 12/May/11 ]|
BTW: if this isn't hard to fix... it may be worth it.
It seems to be the only thing stopping the spring-data-mapping project from working with the latest snapshot drop of the tooling API.
All I had to do to get rid of all the compile errors is convert a few projects that had some groovy code in them to "Groovy projects".
|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.