Releases: spring-projects/sts4
4.17.0.RELEASE
major changes to the Spring Tools 4 for Eclipse distribution
- updated to Eclipse 2022-12 release (new and noteworthy)
fixes and improvements
- (Spring Boot) fixed: Refreshing Live Data over HTTP is not working on VS Code (#872)
- (Spring Boot) fixed: gcPauses -> jvm.gc.pause, memory -> jvm.memory.used (#875)
- (Spring Boot) fixed: live information hovers are broken when running Spring Boot 3 application (#862)
- (Spring Boot) fixed: fetch heap & nonHeap memory metrics together (#874)
- (Spring Boot) fixed: 404 when getting live metrics over HTTP (#879)
- (Spring Boot) fixed: [validation] Spring Boot support range validation messages appear and disappear again (#887)
- (Spring Boot) fixed: [validation] check for superfluous @repository annotations on standard Spring Data repositories (#898)
- (Spring Boot) fixed: [validation] prepare version validation for 4.17.0 release (#904)
- (Spring Boot) fixed: [validation] changing the preferences while language server is not around doesn't have any effect (#836)
- (Spring Boot) fixed: [validation] convert autowired field to constructor should not run on test classes (#902)
- (Spring Boot) fixed: [validation] add preferences to boot version and generation validations (#884)
- (Spring Boot) fixed: [validation] add validations for new Spring Boot versions in general (#885)
- (Spring Boot) fixed: [refactoring] convert autowired field to constructor should make field final (#896)
- (Spring Boot) fixed: [refactoring] [validation] final polishing work (#911)
- (Spring Boot) fixed: [refactoring] convert project to Spring Boot 3 doesn't update Java to 17 anymore (#909)
- (Spring Boot) fixed: [refactoring] when converting a project to Spring Boot 3, always use the latest 3.0.x version (#869)
- (Spring Boot) fixed: [refactoring] OutOfMemoryError: Java Heap Space (#899)
- (Spring Boot) fixed: [refactoring] Exception when trying to convert project (#900)
- (Spring Boot) fixed: [refactoring] converting a simple rest service guide to Spring Boot 3 fails (#867)
- (Spring Boot) fixed: [refactoring] open rewrite refactoring menu item is broken when no language server is running (#865)
- (Spring Boot) fixed: [refactoring] enhance Spring Boot version validation with quick fix to update (#886)
- (Spring Boot) fixed: [refactoring] converting petclinic to Spring Boot 3 results in broken project (#864)
- (Spring Boot) fixed: [refactoring] Migrate Boot 2 auto-config to Boot (#908)
- (Eclipse) fixed: update signing certificate for pre-built third-party bubdles (#852)
- (Eclipse) fixed: remove dependencies on yedit (#870)
- (Eclipse) fixed: Upgrade commons-text-1.9.jar (#892)
- (Eclipse) fixed: Add checksums at download page (#906)
- (Eclipse) fixed: NPE in Eclipse TextMate Grammar preference page (#912)
- (VSCode) fixed: make sure VSCode shows an error message when running on a JDK <17 (#903)
- (VSCode) enhancement: Add shortcut to dashboard (#876) - contributed by Eskibear)
- (VSCode) enhancement: refine walkthrough steps (#907) - contributed by Eskibear)
- (VSCode) enhancement: update walkthrough about creating projects (#916) - contributed by Eskibear)
- (Concourse) fixed: vscode-concourse: add dark background to light mode icon (#845) - contributed by bmalehorn
- (Concourse) fixed: Concourse extension doesn't know about "pre_without_version" and "build_without_version" for a semver resource (#849)
4.16.1.RELEASE
major changes to the Spring Tools 4 for Eclipse distribution
- early access builds available for Spring Tools 4 on Eclipse 2022-12 milestones
important note for upgrading from a release prior to 4.16.0 on Eclipse
- If you are upgrading an existing Spring Tools 4 for Eclipse distribution 4.15.3 or older to 4.16.1, please take a look at the necessary manual steps described for the upgrade to 4.16.0.
fixes and improvements
- (Spring Boot) fixed: Spring XML Config support does not show symbols with scope "File" (#860)
- (Spring Boot) fixed: [open-rewrite] exception when executing quick fix for project (#853)
- (Spring Boot) fixed: [refactoring] quick fix to convert autowired field to constructor param shows up even if the constructor param already exists (#815)
- (VSCode) fixed: Vscode Spring Boot Tools 1.39.0 prevents Java project from Running/Debugging (#847)
- (Eclipse) fixed: Web Tools Platform (WTP) validation is activated by default (#859)
- (Eclipse) fixed: ask user to save dirty editors before deploying on docker (#803)
4.16.0.RELEASE
major changes to the Spring Tools 4 for Eclipse distribution
- updated to Eclipse 2022-09 release (new and noteworthy)
- new distribution build for Linux on ARM included now (experimental) - downloads are here
- m2e 2.0.5 release included in distribution builds for Eclipse
important note for upgrading from a previous installation on Eclipse
- Due to the major update to m2e 2.0 that comes with the Eclipse 2022-09 release, several additional third-party m2e connector extensions that the Spring Tools 4 for Eclipse distribution had installed in the past are no longer compatible. This prevents the automatic update of installations of Spring Tools prior to 4.16.0 to the new release. There are two options how to mitigate this:
- start with a fresh install of Spring Tools 4.16.0 for Eclipse
- go to the
Preferences -> Installation Details
and uninstall the following features via theUninstall
button, then restart the IDE, do aCheck for Updates
, and do the upgrade.Maven Integration for Eclipse JDT Annotation Processor Toolkit
m2e connector for mavenarchiver pom properties
m2e connector for build-helper-maven-plugin
- Eclipse 2022-09 comes with ANSI coloring for the console view built-in, so we don't need to third-party extension
Ansi Console
anymore. If you upgrade an existing installation, please uninstall this extension prior or after upgrading Spring Tools 4 for Eclipse.
fixes and improvements
- (Spring Boot) fixed: Workspace symbol null on custom annotations (#818)
- (Spring Boot) fixed: organize imports causes communication issues with the language server (#806)
- (Spring Boot) enhancement: Quick fix action to refactor field injection to constructor injection (#522)
- (Spring Boot) fixed: Workspace symbol null on custom annotations (#818)
- (Eclipse) enhancement: adapt boot launch support to new platform-enabled ansi console coloring support (#823)
- (Eclipse) fixed: cleanup/remove more entries from Error Log (#802)
- (Eclipse) fixed: switch live hovers in Eclipse to direct-connect after launch (#832)
- (Eclipse) fixed: add switch in boot launch config to enable/disable automatic live hover connect (#843)
- (Eclipse) fixed: live hover auto-connect on launch should check for actuators (#842)
- (Eclipse) enhancement: spring tool suite linux arm distribution (#841)
- (VSCode) fixed: Extension never activates, throwing error "Header must provide a Content-Length property" (#811)
- (Concourse) fixed: Concourse extension doesn't know about "check_every: never" for a resource (#816)
- (Concourse) fixed: Concourse extension doesn't know about "depth" for a semver resource (#830)
- (Concourse) fixed: Concourse extension doesn't recognize URL for "registry_mirror" with a docker-image resource (#831)
- (Concourse) fixed: vscode-concourse: support both .yml and .yaml files (#838) - contributed by bmalehorn
- (Concourse) fixed: vscode-concourse: add language icon for pipelines & tasks (#839) - contributed by bmalehorn
4.15.3.RELEASE
fixes and improvements
- (Spring Boot) fixed: Spring Boot Tools slow down code complete (#808)
- (Language Server) fixed: Copied files should retain copyright ownership (#807)
known issues
- (Eclipse): Due to additional third-party add-ons being installed by default into the Spring Tools 4 for Eclipse distribution, the Maven POM file editor still uses the old XML editor when selecting the source page of that editor (instead of the new, XML language server based one). You can workaround that by manually opening the
pom.xml
file withOpen With
and select theGeneric Editor
.
4.15.2.RELEASE
fixes and improvements
- (Spring Boot) fixed: Validation errors on @@ placeholders in YAML editor (#711)
- (VSCode) fixed: Live process is not auto connected when app is launched in internalConsole (#794)
- (Eclipse) fixed: Cleanup / reduce verbosity of diagnostic output in Eclipse logs (#798)
- (Eclipse) fixed:
Not properly disposed SWT resource
was caused Spring Starter Project (#797) - (Eclipse) fixed: avoid live hover connection attempt when deploying app to docker without actuator (#716)
- (Eclipse) fixed: Devtools integration with boot dash docker is broken (#724)
- (Eclipse) fixed: Pause / Resume for docker boot dash malfunctions (#783)
- (Concourse) fixed: Concourse extension (in vscode) doesn't allow on_error in Steps (#737)
known issues
- (Eclipse): Due to additional third-party add-ons being installed by default into the Spring Tools 4 for Eclipse distribution, the Maven POM file editor still uses the old XML editor when selecting the source page of that editor (instead of the new, XML language server based one). You can workaround that by manually opening the
pom.xml
file withOpen With
and select theGeneric Editor
.
4.15.1.RELEASE
fixes and improvements
- (Spring Boot) fixed: VScode incorrectly suggests removing @Autowired annotation from methods (#787)
- (Spring Boot) fixed: VScode quick fix should not suggest removing @Autowired annotation from JUnit tests (#786)
- (Eclipse) fixed: Not able to extract the new version of spring-tool-suite-4-4.15.0.RELEASE-e4.24.0-win32.win32.x86_64.self-extracting.jar on windows 11 (#788)
- (Eclipse) fixed: Cannot open Spring Boot Language Server Java Editor settings menu (#789)
known issues
- (Eclipse): Due to additional third-party add-ons being installed by default into the Spring Tools 4 for Eclipse distribution, the Maven POM file editor still uses the old XML editor when selecting the source page of that editor (instead of the new, XML language server based one). You can workaround that by manually opening the
pom.xml
file withOpen With
and select theGeneric Editor
.
4.15.0.RELEASE
major changes to the Spring Tools 4 for Eclipse distribution
- updated to Eclipse 2022-06 release (new and noteworthy)
fixes and improvements
- (Spring Boot) fixed: vscode-sts: an edge case of workspace symbol for @PutMapping (#781)
- (VSCode) fixed: Failed to refresh live data from process 12704 - com.xxxx.xx.xxx.BillingServiceApp after retries: 10 (#748)
- (Eclipse) fixed: The Spring Boot Language Server is not immediately shutdown after closing the last open editor to avoid the need to restart the server when you open the next file (related to #568)
- (Eclipse) fixed: When opening symbols, open the compilation unit from the relevant project (#769)
- (Eclipse) fixed: The issue with the internal web browser not being able to open HTTP URLs on macOS got fixed. If you prefer to use the internal browser instead of an external one, you can make that switch in the preferences.
- (Concourse) fixed: Update Concourse registry-image schema (#777)
- (Concourse) fixed: Add registry_mirror & across as a known properties (#752)
known issues
- (Eclipse): Due to additional third-party add-ons being installed by default into the Spring Tools 4 for Eclipse distribution, the Maven POM file editor still uses the old XML editor when selecting the source page of that editor (instead of the new, XML language server based one). You can workaround that by manually opening the
pom.xml
file withOpen With
and select theGeneric Editor
.
4.14.1.RELEASE
import changes
- (VSCode) enhancement: live hovers are now automatically show up when you launch a Spring Boot application in VSCode. Additional JVM args for the Spring Boot app to enable JMX are added to the launch automatically. More details can be found in the user guide section about Live Application Information.
fixes and improvements
- (Spring Boot) fixed: use
startupSnapshot
instead ofstartup
timer call to avoid wiping out the underlying data - (Spring Boot) fixed: When vscode opens a Java project for about 2 hours, the suggestion function will fail (#750)
- (VSCode) improvement: add extension APIs to get live data (#751) - contributed by @Eskibear
known issues
-
(Eclipse): There is an issue with the internal web browser opening HTTP URLs on macOS, showing an error popup from the operating system instead of opening the HTTP URL. Therefore, the default setting has changed to use the external system browser by default.
-
(Spring Boot): Importing Spring Guides into the IDE using Gradle can result in an exception error dialog showing up, complaining about an incompatible class file version. This is most likely due to the IDE running on the embedded JDK17 by default, but the Gradle version in some Spring Guides is not yet updated to a JDK17-compatible version of Gradle. If you face this issue, please import the Spring Guide using Gradle, as usual, ignore the error dialog, and switch to Gradle 7.3 in the
gradle-wrapper.properties
file of the imported project. Then trigger a refresh of the Gradle project using the context menu.
4.14.0.RELEASE
major changes to the Spring Tools 4 for Eclipse distribution
- updated to Eclipse 2022-03 release (new and noteworthy)
fixes and improvements
- (VSCode) fixed: VSCode Spring boot tools 1.30.0 error trying to find JVM (#726)
- (VSCode) fixed: vscode "Problems" diagnostic entries lack "source" field (#725)
- (VSCode) fixed: orphan vscode extension processes left running (#704)
- (VSCode) fixed: deadlock in language server process avoids process to be shutdown (#741)
- (VSCode) fixed: Outline View is broken again on Windows (#742)
- (VSCode) fixed: boot-java.live-information.automatic-tracking.on is not working on vscode (#733)
- (VSCode) fixed: Java 17 is mis-identified as Java 8 (#713)
- (Eclipse) fixed: Deadlock with Spring LSP in Eclipse 4.23 with STS 4.23 nightlies (#729)
known issues
-
(Eclipse): There is an issue with the internal web browser opening HTTP URLs on macOS, showing an error popup from the operating system instead of opening the HTTP URL. Therefore, the default setting has changed to use the external system browser by default.
-
(Spring Boot): Importing Spring Guides into the IDE using Gradle can result in an exception error dialog showing up, complaining about an incompatible class file version. This is most likely due to the IDE running on the embedded JDK17 by default, but the Gradle version in some Spring Guides is not yet updated to a JDK17-compatible version of Gradle. If you face this issue, please import the Spring Guide using Gradle, as usual, ignore the error dialog, and switch to Gradle 7.3 in the
gradle-wrapper.properties
file of the imported project. Then trigger a refresh of the Gradle project using the context menu.
4.13.1.RELEASE
fixes and improvements
- (Spring Boot) improvement: Consider if content assist can be offered for spring.config.import property keys (#536)
- (Spring Boot) fixed: YAML editor generates wrong EOL characters in Windows (#709)
- (VSCode) fixed: Always pop up a prompt box: indexing spring boot properties (#697)
- (VSCode) fixed: Spring Boot Tools for VS Code incorrectly misidentifies internal JDK for Language Support for Java as a JRE (#715)
- (Eclipse) fixed: Create or modify new project - maven update problem (#703)
known issues
-
(Eclipse): There is an issue with the internal web browser opening HTTP URLs on macOS, showing an error popup from the operating system instead of opening the HTTP URL. The best way to workaround this is to switch to an external browser in the preferences via
Preferences -> General -> Web Browser
and then selectUse External Web Browser
. -
(Spring Boot): Importing Spring Guides into the IDE using Gradle can result in an exception error dialog showing up, complaining about an incompatible class file version. This is most likely due to the IDE running on the embedded JDK17 by default, but the Gradle version in some Spring Guides is not yet updated to a JDK17-compatible version of Gradle. If you face this issue, please import the Spring Guide using Gradle, as usual, ignore the error dialog, and switch to Gradle 7.3 in the
gradle-wrapper.properties
file of the imported project. Then trigger a refresh of the Gradle project using the context menu.