4.19.1.RELEASE
updates to the Spring Tools 4 for Eclipse distribution
- early-access builds available for early Eclipse 2023-09 milestones (via the Eclipse Marketplace or the corresponding update site)
fixes and improvements
- (Spring Boot) fixed: Evaluate Spring Modulith actuators (#953)
- (Spring Boot) fixed: No classpath update after source is saved (#987)
- (Spring Boot) fixed: duplicates of symbols showing up (#10056)
- (Spring Boot) fixed: WebSecurityConfigurerAdapter quick fix not showing (#1062)
- (Spring Boot) fixed: Let show optional: prefix for spring.sql.init.schema-locations and spring.sql.init.data-locations (#1067)
- (Spring Boot) fixed: index cache not working after project update (#1079)
- (Spring Boot) fixed: Spring Boot language server interfering with Eclipse Gradle Buildship automatic project synchronization (#1087)
- (VSCode) fixed: Spring Boot Tools vscode extension error popup: Request textDocument/definition failed (#1076)
- (Eclipse) fixed: class loading exception: SpringModelLanguageServer cannot be found (#1060)
- (Eclipse) fixed: add public PGP key to installation as trusted key (#1088)
- (Eclipse) fixed: Contribute pgp trusted key for spring (#1089)
- (Documentation) fixed: Use Theia Blueprint in the documentation? (#1073)
- (build infrastructure) fixed: [GHA Build] Factor out osx distro sign, dmg, notarize upload and linux distro upload out of maven build (#1074)
known issues
-
(Spring Boot): the newly introduced additional reconciling for Java source files which is used to show up additional validations and quick fixes can still cause increased memory and CPU consumption. In case you stumble upon issues in this area, please disable the reconciling via
Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) orPreferences -> Spring -> Open Rewrite
(in Eclipse). A fix for this that significantly reduces CPU and memory consumption here is being worked on and is scheduled for the upcoming4.20.0
release. -
(Eclipse): It still seems to happen sometimes that resource files like the
application.properties
do not get copied correctly into the target folders after changing those files, sometimes those resource files disappear from the target folder entirely. We are investigating the problem and will provide updates and workaround on issue #929.