[GRADLE-2768] Eclipse tooling api client would like to know 'derived' directories Created: 07/May/13 Updated: 10/Feb/17 Resolved: 10/Feb/17
This relates to https://issuetracker.springsource.com...
Essentially, many Eclipse tools treat resources that are marked as 'derived' specially. Though in many cases this doesn't matter... in some cases it is crucial for logical and efficient processing.
I have hard-coded the Gradle STS tooling now to mark any folder called 'build' nested under a project folder as 'derived'.
That does work... but I suspect this is only convention and it is possible for builds to customize where this folder is.
So for a truly correct implementation I would need to ask the tooling API where this folder is for a given project.
Is this currently supported? How?
If no, could this be added in the future.
|Comment by Gradle Forums [ 07/May/13 ]|
At the moment, the location of build dir is not available via the tooling api.
It's hard to say when we will look into providing you the api that solves the use case. I'll export a jira ticket.
Hope that helps!
|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.