Uploaded image for project: 'Spring Tool Suite'
  1. Spring Tool Suite
  2. STS-2460

Gradle classpath container should distinguish exported / non-exported dependencies

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.9.0.RC1
    • Fix Version/s: None
    • Component/s: GRADLE

      Description

      See forum thread: http://forum.springsource.org/showthread.php?123333-Gradle-import-produces-wrong-classpath-files&p=402394#post402394

      This issue is blocked by http://issues.gradle.org/browse/GRADLE-2114

      Workaround: don't use 'Enable Dependency Management' option in the import wizard. This switches STS into a mode where it uses the generated .classpath file from the Gradle eclipse plugin instead of the tooling API information to configure the eclipse classpath.

      This workaround requires STS 2.9.0.RC1 or above.

        Activity

        Hide
        mlippert Martin Lippert added a comment -

        Since we no longer pushing this project forward and recommend to use the Buidship project at Eclipse instead, I am closing this issue as won't fix.
        If you would like to add comments and/or re-open the issue, please file a new issue at https://github.com/spring-projects/eclipse-integration-gradle

        Show
        mlippert Martin Lippert added a comment - Since we no longer pushing this project forward and recommend to use the Buidship project at Eclipse instead, I am closing this issue as won't fix. If you would like to add comments and/or re-open the issue, please file a new issue at https://github.com/spring-projects/eclipse-integration-gradle

          People

          • Assignee:
            kdvolder Kris De Volder
            Reporter:
            kdvolder Kris De Volder
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: