STS 2.7.0.M2 released

[Martin Lippert]

Dear Spring Community,

I'm pleased to announce that we just released the second milestone build for the next release of the SpringSource Tool Suite (STS).

This milestone brings mostly new features for the Cloud Foundry support and Groovy&Grails developers, including:

• Improved Cloud Foundry support
• Support for Grails 1.4
• Grails aware Rename Type Refactoring
• Improved content assist for GSPs
• Improved Gradle support

More details can be found in the New and Noteworthy for 2.7.0.M2 document. Detailed installation instructions are also available, please look at the installation from the milestone update sites.

As always downloads are available from the STS download page, check "Other Downloads".

The release is planned for the beginning of July.

Regards,
Martin

[Brad Murray]

I realize you guys are working quite hard on this, is there any ETA on the 3.1 support?

[Martin Lippert]

Did you try Spring 3.1.0.M2 with STS 2.7.0.M2? It should work a lot better and not produce those tedious errors that we had before using 3.1.0.M1 of Spring.
With regards to the full support: 2.7.0 will ship at the beginning of July and that version should work with 3.1.0 versions of the Spring framework. We won't have special dedicated IDE support for some of the new features, but that will ship with STS 2.8.0 (that is at least the plan right now).

HTH,
Martin

[rherrick]

Is this going to be compatible with my existing workspaces created with 2.6.1? I really don't relish the idea of having to recreate my workspaces yet again, but I'd really like to work with the updated Grails and Gradle support.

Is it ever going to be possible to actually, you know, UPGRADE STS as opposed to a complete new installation? I realize this is an Eclipse issue, not an STS issue, but it is quite frustrating...

[Martin Lippert]

Hi!

Is this going to be compatible with my existing workspaces created with 2.6.1? I really don't relish the idea of having to recreate my workspaces yet again, but I'd really like to work with the updated Grails and Gradle support.

You can always open existing workspaces with newer versions of STS. There is no need to setup a new workspace.

Is it ever going to be possible to actually, you know, UPGRADE STS as opposed to a complete new installation? I realize this is an Eclipse issue, not an STS issue, but it is quite frustrating...

Eclipse/STS allows you to upgrade existing installations to never versions. Once a new release version is out, you can "check for updates" and install the new version right into your existing installation. If you wanna upgrade from a release version to a newer milestone version, you would need to deactivate the default STS update site and add the milestone update site. Then select "check for updates" again and you will see the milestone version showing up and you can install it again directly into your existing STS installation.

HTH,
Martin

[rherrick]

You can always open existing workspaces with newer versions of STS. There is no need to setup a new workspace.

I actually had a lot of issues back in the 2.3.x and 2.5.x versions going from, e.g., 2.3.0 to 2.3.1 because of changes in server configuration, etc. I'll take your word for it that my 2.6.x workspaces will work properly though!

Eclipse/STS allows you to upgrade existing installations to never versions. Once a new release version is out, you can "check for updates" and install the new version right into your existing installation. If you wanna upgrade from a release version to a newer milestone version, you would need to deactivate the default STS update site and add the milestone update site. Then select "check for updates" again and you will see the milestone version showing up and you can install it again directly into your existing STS installation.

I hadn't found this capability before. I'll try to run with this and see how it works. Thanks a lot for the info! If anyone else needs a pointer to the appropriate update site URLs, the process is described in this document.

Thanks!

[d_cavestro]

Hi guys,
after I upgraded to 2.7.0.M2 the IDE always starts with an empty workspace (it forgets the last opened one).
Is there any known reason?

[bauna]

Hey I have the same issue. Changing the workspaces prefs does not work.
Is there any workaround?

Thanks!

Hi guys,
after I upgraded to 2.7.0.M2 the IDE always starts with an empty workspace (it forgets the last opened one).
Is there any known reason?

[Martin Lippert]

Hey!

Hm, sounds strange, never saw this. Does STS starts with a different, empty workspace and you can switch back to your old, still existing workspace? Or is your old workspace wiped out somehow?

-Martin

[d_cavestro]

Hi Martin,
always the former: STS starts with a different, empty workspace and I can switch back to my old, still existing workspace.

Cheers
Davide

Hey!
Does STS starts with a different, empty workspace and you can switch back to your old, still existing workspace? Or is your old workspace wiped out somehow?

-Martin