This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

STS & GGTS 3.3.0 released

we are happy to announce the next major release of our Eclipse-based tooling today: The Spring Tool Suite (STS) 3.3.0 and the Groovy/Grails Tool Suite (GGTS) 3.3.0.

Highlights from this release include:

Eclipse Kepler Release updates (including Mylyn, EGit, m2e, m2e-wtp)

updated bundled tc Server to 2.9.2 and bundled Spring Roo to 1.2.4

ready for Spring 4

support for JavaConfig-driven Spring projects (including navigation support for @Autowired)

new and unified "New Spring Project" wizard

additional performance improvements for working with Spring projects

brand new instant and lightning fast quick search for your workspace

GGTS now includes grails 2.2.3

We continue to ship distributions on top of the latest Eclipse release (Eclipse Kelper 4.3) as well as Eclipse Juno 3.8. While the 3.8-based version ships with all the components from Eclipse Juno, only the 4.3-based version ships on top of the just released Eclipse Kepler 4.3 version and is therefore the only distribution that comes with all the latest fixes and improvements from Eclipse Kepler.

Updates from STS/GGTS 3.x are available through the automatic "Check for Updates". Users of STS 2.9.x (or older) should start with a fresh installation of STS/GGTS 3.3.0.

The next version 3.4.0 is scheduled to arrive in October 2013, shortly after the Eclipse Kepler SR1 (4.3.1) release. Also watch out for milestone builds of 3.4.0 if you want to stay up-to-date with the latest developments. And meet the team at this years SpringOne2GX conference.

we are happy to announce the next major release of our Eclipse-based tooling today: The Spring Tool Suite (STS) 3.3.0 and the Groovy/Grails Tool Suite (GGTS) 3.3.0.

Highlights from this release include:

Eclipse Kepler Release updates (including Mylyn, EGit, m2e, m2e-wtp)

updated bundled tc Server to 2.9.2 and bundled Spring Roo to 1.2.4

ready for Spring 4

support for JavaConfig-driven Spring projects (including navigation support for @Autowired)

new and unified "New Spring Project" wizard

additional performance improvements for working with Spring projects

brand new instant and lightning fast quick search for your workspace

GGTS now includes grails 2.2.3

We continue to ship distributions on top of the latest Eclipse release (Eclipse Kelper 4.3) as well as Eclipse Juno 3.8. While the 3.8-based version ships with all the components from Eclipse Juno, only the 4.3-based version ships on top of the just released Eclipse Kepler 4.3 version and is therefore the only distribution that comes with all the latest fixes and improvements from Eclipse Kepler.

Updates from STS/GGTS 3.x are available through the automatic "Check for Updates". Users of STS 2.9.x (or older) should start with a fresh installation of STS/GGTS 3.3.0.

The next version 3.4.0 is scheduled to arrive in October 2013, shortly after the Eclipse Kepler SR1 (4.3.1) release. Also watch out for milestone builds of 3.4.0 if you want to stay up-to-date with the latest developments. And meet the team at this years SpringOne2GX conference.

That could be, we don't ship updates of all the components of the distribution as copy from our update repository. Therefore upgrading an existing STS installation will pick up changes from the main Eclipse update site for the underlying distribution (Juno, for example) and our own STS components.

The reason is that the STS version for a certain Eclipse version ships with the components from that Eclipse train. So if you have an STS version based on Eclipse Juno, you will get updates for all those components from the Juno train. If Juno SR1 comes out and that contains a new version of EGit, you would get that, I think.

But if you have a Juno-based version of STS installed and update to a newer version of STS, you are still on Eclipse Juno. Therefore you will still get updates for those Eclipse components only if they are updated on the Eclipse Juno repository, which is only the case for SR1 and SR2 releases.

That is at least what I am guessing happens for you. The main Eclipse version is not updated automatically from Juno to Kepler.

But you can update the EGit version yourself by adding the EGit update repository to the "install new software" dialog, select the new 3.0 components and install them. The dialog will figure out that this is an update to those components instead of a new installation.

HTH,
Martin

Comment

Okay, that makes sense. So what I really need to do is download the whole STS install, which is based on the latest Eclipse rather than just do an update within my existing version, which could be Juno, etc.

That could be, we don't ship updates of all the components of the distribution as copy from our update repository. Therefore upgrading an existing STS installation will pick up changes from the main Eclipse update site for the underlying distribution (Juno, for example) and our own STS components.

The reason is that the STS version for a certain Eclipse version ships with the components from that Eclipse train. So if you have an STS version based on Eclipse Juno, you will get updates for all those components from the Juno train. If Juno SR1 comes out and that contains a new version of EGit, you would get that, I think.

But if you have a Juno-based version of STS installed and update to a newer version of STS, you are still on Eclipse Juno. Therefore you will still get updates for those Eclipse components only if they are updated on the Eclipse Juno repository, which is only the case for SR1 and SR2 releases.

That is at least what I am guessing happens for you. The main Eclipse version is not updated automatically from Juno to Kepler.

But you can update the EGit version yourself by adding the EGit update repository to the "install new software" dialog, select the new 3.0 components and install them. The dialog will figure out that this is an update to those components instead of a new installation.

I would recommend that, yes. It is sometimes a good choice to start with a fresh installation.
In case you have additional plugins installed and find that work of installing all of them again after a fresh installation, there is a script that might help you with that work. You can configure that script to install a bunch of plugins from various update sites at once and run it from the command line:

Comment

I was running gsts 3.0.0. I updated to the latest ... 3.3.0 and now anything related to grails is gone. My project lost the grails icon. I am not given the option to create a grails project and so on. I can see the grails components installed.
Any ideas what do I have to do to get my grails support back in gsts ?

It looks like something went wrong with the update and now maybe caused a dependency conflict under the hood. The easiest way to resolve this is to start with a fresh GGTS 3.3.0 installation from the distribution downloads.

If you adapt it to your needs, you could use it to automatically install a bunch of additional features into an existing installation (like a fresh STS or GGTS one) without going through the "install new software" UI in Eclipse/STS/GGTS.

If you would like to dive deeper into the dependency conflict, you can open a console view, switch it to the "Host OSGi console" and type "ss" (for short status) after the prompt. The result is a list of all installed OSGi bundles. Look for anything that is in the state "INSTALLED" (instead of ACTIVE, STARTING, RESOLVED, etc). If there is anything just "INSTALLED", then you can type in "diag" followed by the number of that bundle to get diagnosis information why that bundle could not resolve. But it might be very tricky to resolve this, therefore I would recommend the easy way, starting with a fresh installation.

HTH,
Martin

Comment

Thanks for the response Martin.
Yes that is what I did yesterday after I posted and could not find a way to recover and had to get going with my project.
You are correct that the main issue of fresh install is setting up the set of plugins so I will look into the script.

Thanks

Comment

Hi. Any help is appreciated. Been trying to download the latest zip archive (both kepler and june versions) from http://www.springsource.org/downloads/sts-ggts but the download always seems to hang and then get killed. Anyone else having similar issues?

I updated the download page to contain the "download.springsource.com" versions of the URLs again. Please try again.
If you are still not able to download the distribution, please check firewall and virus scanner options, sometimes they can cause hiccups.