[GRADLE-2015] Tooling API idea / idea plugin does not understand java-base plugin as it does the java plugin Created: 26/Dec/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
Trying to get information about project structure of $GRADLE_HOME/samples/java/base (uses custom source roots) with the following program:
The problem is that the Tooling API doesn't expose custom source roots here.
|Comment by Szczepan Faber [ 16/Jan/12 ]
It's because they don't apply the 'java' plugin.
I'm not sure if it's a bug... or at least nobody every complained that IDE plugins don't work with 'java-base' plugins. E.g. IDE plugins 'work' with the 'java-base' plugin but they won't understand the 'meaning' of the compile/runtime configurations, and thus they will not create a proper java project in the IDE.
|Comment by Denis Zhdanov [ 16/Jan/12 ]
What features are provided by 'java-base'? I've checked gradle documentation page but it has just a couple references to the 'java-base' without any details.
|Comment by Szczepan Faber [ 26/Jan/12 ]
I agree it's not documented well enough. I don't think it is valuable to use instead of the java plugin.
|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.