Skip to content

4.23.0.RELEASE
Compare
Choose a tag to compare
@github-actions github-actions released this 12 Jun 13:46
4.23.0.RELEASE
07eb45a

important highlights

  • (Spring Boot) Syntax validation for JPQL, SQL, HQL embedded in Java code
  • (Spring Boot) Syntax highlighting for SQL embedded into Spring Data query annotations
  • (Spring Boot) Navigation to beans from @DependsOn
  • (Spring Boot) Upgrade to Spring Boot 3.3 is available via OpenRewrite recipes.

updates to the Spring Tools 4 for Eclipse distribution

all fixes and improvements in detail

  • (Spring Boot) verify upgrade support to Spring Boot 3.3.0 #1255
  • (Spring Boot) vscode @DependsOn navigation not linked #1254
  • (Spring Boot) add parser-based validation for JPQL, SQL, HQL snippets #1236
  • (Spring Boot) inlay hint in pom.xml file to upgrade to latest Spring Boot version #1211
  • (Spring Boot) Occasional NPE when opening / importing / creating Maven projects #1257
  • (Spring Boot) Map<K,V> with escaped key not works properly in application.yml #1243
  • (Spring Boot - VSCode) VSCode Spring Boot extension causes semantic token loss upon loading #1260
  • (Spring Boot - VSCode) Variable assignment/reference syntax highlighting lost between v1.53.0 and v1.54.0 #1249
  • (Spring Boot - Eclipse) upgrade with preview in Eclipse throws exception #1258
  • (Spring Boot - Eclipse) Eclipse Run Configuration - Use Temporary Jar becomes secretly unchecked #1248
  • (Eclipse) Eclipse crashes after upgrade of libwebkit2gtk to 2.44.x #1230
  • (Eclipse) The latest release of Eclipse fixed the increased spacing in e.g. the package explorer. No workaround for this needed anymore.

known issues

  • (Eclipse) This release of the Spring Tools for Eclipse ships and requires a JDK 21 to run the IDE on and we added the necessary updates sites to make the upgrade experience as seamless as possible. In case you configured the JDK to run the IDE on manually in the SpringToolSuite4.ini file, make sure to update this configuration to point to a JDK 21. Side note: This change doesn't affect your projects or workspace settings at all. You can continue to configure and use whatever JDK you need inside of your workspaces to compile and run your projects on.
Assets 6
Loading