Important Note
This is a minor bugfix and maintenance release that we ship to our existing STS3 users beyond the announced maintenance lifespan for your convenience. We strongly recommend to update to the new Spring Tools 4. Here is a migration guide from Spring Tool Suite 3 to Spring Tools 4 that helps with migrating an existing workspace.
In case you are missing something extremely important or something is blocking you from upgrading, please raise an issue at: Spring Tools 4 GitHub issues.
Updates and New/Enhanced Features
Eclipse 2020-03 (4.15)
The default STS distribution is now based on the recently released Eclipse 2020-03 (4.15) release. Details about the Eclipse release can be found here: Eclipse 2020-03.
Please remember: the Quick Text Search now part of the Eclipse platform
The Quick Text Search feature got contributed to the Eclipse platform and ships now to all the millions of users of the Eclipse IDE. Therefore this will no longer be a separate feature installed into the Spring Tool Suite 3 distribution, but a default feature of the platform itself. We are pround of this contribution to the platform and welcoming all the new users to this amazing feature.
Important Changes and Fixes
Download STS: https://spring.io/tools3/sts/all
Spring Tools Issue tracker: https://github.com/spring-projects/spring-ide/issues
The new buildpacks attribute in manifest.yml files is not yet supported when deploying apps via the Spring Boot dashboard within STS. A dialog will pop up and warn you about this limitation in case you run into this situation. As a workaround, you can push your apps via the CF CLI or continue to use the deprecated buildpack attribute.
Deleting certain Eureka service instances, like p-service-registry in Pivotal Web Services, from boot dashboard Cloud Foundry targets may experience problems with timeouts. The same issue may be found when deleting them from Eclipse Tools for Cloud Foundry (CFT). A workaround is to use the cf CLI to delete these service instances.
STS 3.9.12 can run on top of a JDK out-of-the-box. However, please notice that the Maven support in Eclipse/STS runs within the JVM of the IDE and therefore also uses the JDK9/10/11/12/13 runtime. While that isn't necessarily a problem, having Maven modules in your build that aren't compatible with Java 9 might cause your project build to fail in Eclipse/STS.
This is the case, for example, if you use Spring Boot 1.5.x or earlier versions, which uses an older version of the Maven jar plugin, which fails when running on top of a Java 9/10/11 VM. In that case we recommend to configure Eclipse/STS to run on top of a Java 8 runtime (by modifying the eclipse.ini or sts.ini file accordingyly).
The Spring Boot Dashboards ngrok tunnel feature doesn't work yet with remote service registries from Spring Cloud Services. Instead it works with self-deployed Eureka service registry apps on CF only (as described here). We are working on enhancing the ngrok tunnel feature to directly support Spring Cloud Services in the near future. In the meantime we published a tech note that describes how to setup ngrok tunneling in combination with SCS manually.
Workaround is open launch configuration for the Boot App. Navigate to Spring Boot tab and enter a boot property into "Override Properties" table. For example server.port and value 8080. Save the launch configuration and re-launch your Boot App.
STS 3.9.12 requires a JDK8+ to run on top of. Nevertheless the native Eclipse launcher component might pick up a JRE or an older JDK automatically if you don't specify which JDK to run STS on top of. To avoid this, you can specify the JDK in the sts.ini file that comes with your STS installation. Add a line at the beginning "-vm" and an additional line below that which points to the "javaw" executable of the JDK on your machine. Here is a detailed explanation how to configure the JVM in the ini file.