[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

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

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


Trying to get information about project structure of $GRADLE_HOME/samples/java/base (uses custom source roots) with the following program:

package org.jetbrains.plugins.gradle;

import org.gradle.tooling.GradleConnector;
import org.gradle.tooling.ModelBuilder;
import org.gradle.tooling.ProjectConnection;
import org.gradle.tooling.model.idea.*;

import java.io.File;

 * @author Denis Zhdanov
 * @since 12/8/11 5:07 PM
public class GradleStartClass {

  private static final String GRADLE_TO_USE = "/home/denis/dev/gradle/gradle-1.0-milestone-7-20111219065105+0100";
  private static final String GRADLE_PROJECT_PATH = "/home/denis/dev/gradle/gradle-1.0-milestone-6/samples/java/base";

  public static void main(String[] args) {

  private static void showDependencies() {
    GradleConnector connector = GradleConnector.newConnector();
    connector.useInstallation(new File(GRADLE_TO_USE));
    connector.forProjectDirectory(new File(GRADLE_PROJECT_PATH));
    ProjectConnection connection = connector.connect();
    ModelBuilder<? extends IdeaProject> modelBuilder = connection.model(IdeaProject.class);
    IdeaProject project = modelBuilder.get();
    System.out.println("-----------------> Listing modules <----------------");
    for (IdeaModule module : project.getModules()) {
      System.out.printf("    -----------------> Module %s <----------------%n", module.getName());
      for (IdeaContentRoot contentRoot : module.getContentRoots()) {
        System.out.println("      Content root " + contentRoot.getRootDirectory());
        System.out.println("      Source directories:");
        for (IdeaSourceDirectory directory : contentRoot.getSourceDirectories()) {
          System.out.println("        " + directory.getDirectory());
    System.out.println("-----------------> Finishing <----------------");


-----------------> Listing modules <----------------
    -----------------> Module test <----------------
      Content root /home/denis/dev/gradle/gradle-1.0-milestone-6/samples/java/base/test
      Source directories:
    -----------------> Module base <----------------
      Content root /home/denis/dev/gradle/gradle-1.0-milestone-6/samples/java/base
      Source directories:
    -----------------> Module prod <----------------
      Content root /home/denis/dev/gradle/gradle-1.0-milestone-6/samples/java/base/prod
      Source directories:
-----------------> Finishing <----------------

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:

  • 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:10:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.