Spring Tool Suite
  1. Spring Tool Suite
  2. STS-734

support runtime installation in shared install environments

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0.RELEASE
    • Fix Version/s: 2.5.0.RC1
    • Component/s: GRAILS
    • Labels:

      Description

      Steps:
      1. Make STS folder read-only for current user
      2. Install Grails feature from Extensions tab

      Logged error: I/O Error while copying /tmp/springsource/sts-2.3.0.RELEASE/plugins/org.codehaus.grails.bundle_1.1.2/content - see details.

      The actual install location is /home/stp/.eclipse/com.springsource.sts_2.3.0.RELEASE_496601317/plugins/org.codehaus.grails.bundle_1.1.2/ in this case.

        Activity

        Hide
        Kris De Volder (c) added a comment -

        While I'm not 100% sure of this, I think that some stuff that was committed around this issue has broken the GrailsConfiguration.

        It seems that STS is no longer picking up the Grails install sitting alongside STS automatically anymore.

        This is causing all of the Grails UI tests to fail because a Grails install cannot be found to execute Grails commands. It also means that I can no longer run any Grails related tests locally either.

        For an example of the tests failing: see this screenshot from the SWTBot tests.

        https://build.springsource.com/browse/STS-TEST35-469/artifact/SWTBot-Screenshots/screenshot-TestInplaceDialog.testStatusLineForBogusProjects.jpeg

        Notice the "No grails configuration ..." message displayed in the dialog.

        Before the changes committed on that particular build, the Grails install was configured automatically if it was found in the right place. Now, it seems we have to manually configure Grails installs.

        Show
        Kris De Volder (c) added a comment - While I'm not 100% sure of this, I think that some stuff that was committed around this issue has broken the GrailsConfiguration. It seems that STS is no longer picking up the Grails install sitting alongside STS automatically anymore. This is causing all of the Grails UI tests to fail because a Grails install cannot be found to execute Grails commands. It also means that I can no longer run any Grails related tests locally either. For an example of the tests failing: see this screenshot from the SWTBot tests. https://build.springsource.com/browse/STS-TEST35-469/artifact/SWTBot-Screenshots/screenshot-TestInplaceDialog.testStatusLineForBogusProjects.jpeg Notice the "No grails configuration ..." message displayed in the dialog. Before the changes committed on that particular build, the Grails install was configured automatically if it was found in the right place. Now, it seems we have to manually configure Grails installs.

          People

          • Assignee:
            Steffen Pingel
            Reporter:
            Steffen Pingel
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: