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

Updating more than one plugin from Grails plugin manager is very long-winded

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 2.5.0.M3
    • Fix Version/s: 2.5.0.RC1
    • Component/s: None
    • Labels:
      None

      Description

      If a user selects more than one plugin to update from the Grails Plugin Manager, the process of upgrading them is very long-winded:

      1. The user must first confirm the upgrade of a plugin
      2. Then STS updates the Grails dependencies
      3. Finally the workspace is rebuilt

      This sequence is done for every plugin the user wants to update. One option would be to simply put the new version numbers in application.properties, run grails compile, automatically answer 'y' to each upgrade question, and then refresh the dependencies and rebuild the workspace just the once.

        Activity

        Hide
        Kris De Volder (c) added a comment -

        I don't think this has ever been something we did. In general our tools are as much as possible just UI on top of the grails commandline commands.

        Personally, I would be very hesitant to make our tools depend on directly modifying grails properties files. One reason is that we'd be more likely to have things break when switching between grails versions.

        So, if we need to have some way of installing multiple plugins at a time without booting-up grails each time, (which I agree seems desisarable) we'd need a grails command that provides similar functionality.

        Show
        Kris De Volder (c) added a comment - I don't think this has ever been something we did. In general our tools are as much as possible just UI on top of the grails commandline commands. Personally, I would be very hesitant to make our tools depend on directly modifying grails properties files. One reason is that we'd be more likely to have things break when switching between grails versions. So, if we need to have some way of installing multiple plugins at a time without booting-up grails each time, (which I agree seems desisarable) we'd need a grails command that provides similar functionality.
        Hide
        Kris De Volder (c) added a comment -

        I'm closing this. I think that avoiding multiple refresh dependencies and builds is the best we can do at the moment, lacking a grails command to install multiple plugins at once.

        Show
        Kris De Volder (c) added a comment - I'm closing this. I think that avoiding multiple refresh dependencies and builds is the best we can do at the moment, lacking a grails command to install multiple plugins at once.
        Hide
        Kris De Volder (c) added a comment -

        Talked about this with Andrew. We can't do what Peter suggests (modifying directly in application.properties) now, because our dependency refreshing code is too shaky to make this work now. But it seems like eventually we should be able to get this working.

        So I reopened this but took of the "Fix for RC1".

        Show
        Kris De Volder (c) added a comment - Talked about this with Andrew. We can't do what Peter suggests (modifying directly in application.properties) now, because our dependency refreshing code is too shaky to make this work now. But it seems like eventually we should be able to get this working. So I reopened this but took of the "Fix for RC1".
        Hide
        Peter Ledbrook added a comment -

        The current behaviour is fine and I would leave it at that. As you say, modifying application.properties is too reliant on underlying behaviour. It also won't work with plugins declared in the dependency DSL in BuildConfig.groovy.

        It looks like we'll be having a Grails 1.4, so if you have any requests for that, contact Graeme. Perhaps we can make life easier for you in some of these areas.

        Show
        Peter Ledbrook added a comment - The current behaviour is fine and I would leave it at that. As you say, modifying application.properties is too reliant on underlying behaviour. It also won't work with plugins declared in the dependency DSL in BuildConfig.groovy . It looks like we'll be having a Grails 1.4, so if you have any requests for that, contact Graeme. Perhaps we can make life easier for you in some of these areas.
        Hide
        Kris De Volder (c) added a comment -

        OK, in that case I'll close it for now.

        Show
        Kris De Volder (c) added a comment - OK, in that case I'll close it for now.

          People

          • Assignee:
            Unassigned
            Reporter:
            Peter Ledbrook
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: