[GRADLE-2677] Tooling API: Expose information about buildSrc (if any) Created: 12/Feb/13  Updated: 02/Feb/17  Resolved: 02/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.4
Fix Version/s: None

Type: Bug
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Fixed Votes: 10


Gradle references says the following:

When you run Gradle, it checks for the existence of a directory called buildSrc. Gradle then automatically compiles and tests this code and puts it in the classpath of your build script. You don't need to provide any further instruction.

It looks like an implicitly configured gradle sub-project then. However, tooling api doesn't expose any information about it. Looks like a bug.

Implied by the ticket IDEA-98930

Comment by Ryan Ernst [ 23/Sep/15 ]

Any comment here from gradle folks? This makes developing a large project with buildSrc a pain. Either it is added as a module (which causes warnings/errors in the editor because each class shows up twice, once through the implicit buildSrc dependency, and another in the "extra" module), or it must be setup as a completely separate intellij workspace. I would assume if the tooling api exposed information about buildSrc, it could be setup in intellij so editing could take place without errors, in the same workspace.

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:

  • 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!

Comment by Benjamin Muschko [ 02/Feb/17 ]

I believe this has been fixed with the following:


I am not quite sure if IntelliJ already leverages the new functionality but generally speaking they should be able to. Please open an issue on GitHub if you think that the use case hasn't been fulfilled.

Generated at Wed Jun 30 12:28:27 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.