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

Plugin does not set the Gradle user home using the Tooling API, thus is always default

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0.RELEASE
    • Fix Version/s: 3.2.0.M2
    • Component/s: GRADLE
    • Labels:
      None

      Activity

      Hide
      kdvolder Kris De Volder added a comment -

      To resolve this issue should add a section to the gradle preferences page to be able to specify an alternate location.

      Show
      kdvolder Kris De Volder added a comment - To resolve this issue should add a section to the gradle preferences page to be able to specify an alternate location.
      Hide
      kdvolder Kris De Volder added a comment -

      I've just pushed a fix for this issue. There's now a section on the Gradle preferences page to set Gradle user home and this setting is passed on the tooling API.

      However... it looks like the tooling API is buggy in the sense that it only partially obeys the setting.
      In my 'custom' user home I see a folder 'caches' and 'daemon' that get created with some stuff in them.
      But in my default ~/.gradle folder I am still getting a wrapper folder to which the distributions are getting downloaded.

      I don't beleave this is an STS issue but a gradle tooling API issue so will need to take it up with Gradle devs on their forum or bug tracker.

      Show
      kdvolder Kris De Volder added a comment - I've just pushed a fix for this issue. There's now a section on the Gradle preferences page to set Gradle user home and this setting is passed on the tooling API. However... it looks like the tooling API is buggy in the sense that it only partially obeys the setting. In my 'custom' user home I see a folder 'caches' and 'daemon' that get created with some stuff in them. But in my default ~/.gradle folder I am still getting a wrapper folder to which the distributions are getting downloaded. I don't beleave this is an STS issue but a gradle tooling API issue so will need to take it up with Gradle devs on their forum or bug tracker.
      Hide
      kdvolder Kris De Volder added a comment -

      Closing issue: as far as STS is concerned I think this issue is 'fixed'.

      I've added a comment here on the corresponding Gradle forum thread:
      http://forums.gradle.org/gradle/topics/import_project_into_eclipse_with_sts_using_gradle_wrapper_ignores_jvm_property_dgradle_user_home

      Show
      kdvolder Kris De Volder added a comment - Closing issue: as far as STS is concerned I think this issue is 'fixed'. I've added a comment here on the corresponding Gradle forum thread: http://forums.gradle.org/gradle/topics/import_project_into_eclipse_with_sts_using_gradle_wrapper_ignores_jvm_property_dgradle_user_home
      Hide
      radimk Radim Kubacki added a comment -

      Updating tooling API JAR to Gradle 1.11 or newer should fix remaining part where Gradle distribution was downloaded into default Gradle user home directory.

      Show
      radimk Radim Kubacki added a comment - Updating tooling API JAR to Gradle 1.11 or newer should fix remaining part where Gradle distribution was downloaded into default Gradle user home directory.

        People

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

          Dates

          • Created:
            Updated:
            Resolved: