[GRADLE-1817] Tooling API: keep source roots in sync with content root Created: 29/Sep/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: Bug
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Get a view to the 'gant' project via the Tooling API (ProjectConnection.getModel(BasicIdeaProject.class)). That holds the following data for the module 'gantgroovy1.8'_:

  • module content root is 'gant_groovy1.8';
  • module has a source root 'src/main/groovy';

The problem is that the source root doesn't belong to the file system tree defined by the module content root. That is not supported by IntelliJ IDEA. Basically, the API should expose the second content root for the module then (it's possible to have more than one content root per-module where every content root has a number of its source/test roots).

 Comments   
Comment by Szczepan Faber [ 29/Sep/11 ]

Hey!

gant project maintains the idea configuration in *.iml and *.ipr checked in to the VCS. It is a sort of specialized configuration and if you try to generate idea metadata for this project it's not going to work well. Same for the tooling api.

However, I see the issue with source folders living outside of the content root. I'll see if I can fix it.

Comment by Szczepan Faber [ 29/Sep/11 ]

> Basically, the API should expose the second content root for the module then

The problem is that the second content root points to some upper folder that is already a content root for the parent project. IDEA doesn't like that E.g. I cannot have 2 modules in Idea that have the same content root.

So I don't think we will solve this case soon because it requires completely different approach.

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 [ 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.

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