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

If no *valid* tc server runtime or instance exists in the workspace, STS should properly configure the 'bundled one' automatically.

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.7.0.M2
    • Fix Version/s: None
    • Component/s: EDITING, GRAILS, SERVER
    • Labels:
      None

      Description

      A tc server runtime is automatically configured in a new workspace.
      Also a new tc server insight instance is automatically configured using this runtime.

      However in an old workspace this doesn't happen.

      Specifically, for example, if I installed a new version of STS and deleted the old one. Then run on server on my old workspace won't work anymore.

      Worse still, if I try to create a new server instance, I won't be able to unless I first figure out that I also have to fix the Server runtime configuration. If I don't, I will just be presented with an empty list of choices in the wizard for creating servers. This is a bit confusing since there's absolutely no explanation/error to indicate why the list is empty.

      It would be nice if the autoconfiguration functionality which now gets executed only in a new workspace, could be extended to also take care of configuring the bundled Tc Server runtime even in an old workspace. Especially, if the runtime that is configured in that workspace is invalid/deleted.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Kris De Volder (c)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              First Response Date: