The next generation of tooling for Spring Boot, including support for Cloud Foundry manifest files, Concourse CI pipeline definitions, BOSH deployment manifests, and more... - Available for Eclipse, Visual Studio Code, and Theia
EPL-1.0 License
Bot releases are hidden (Show)
Published by BoykoAlex 6 months ago
<->
.yml conversions available in Eclipse and VSCode<->
.yml converter #739
org.springframework.ide.vscode.boot.java.livehover.v2.SpringProcessTracker
and its references #1221
StsToolingModel
#1201
Published by martinlippert about 1 year ago
(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) or Preferences -> 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 upcoming 4.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.
Published by martinlippert over 1 year ago
(Spring Boot): Even vastly improved over the previous releases, 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, feel free to disable the reconciling via Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) or Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Server -> Open Rewrite
(in Eclipse).
(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
Published by martinlippert over 1 year ago
Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) or Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Server -> Open Rewrite
(in Eclipse).Published by martinlippert over 1 year ago
application.properties
) to not be copied into the target folder anymore. This works again and automatically copies your changed application.properties
file to the target folder, so that those changes are taken into account when running the project automatically again@Autowired
" warning when using abstract classes (#985)Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) or Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Server -> Open Rewrite
(in Eclipse).Published by martinlippert over 1 year ago
(Spring Boot): The newly introduced additional reconciling for Java source files which is used to show up additional validations and quick fixes can cause increased memory and CPU consumption. In case you stumble upon issues in this area, feel free to disable the reconciling via Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) or Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Server -> Open Rewrite
(in Eclipse).
(Eclipse): Due to a bug in the Maven Integration for Eclipse, you might some across the problem that resource files are no longer copied into the target directories (#929). Unfortunately there is no release of the Maven Integration for Eclipse available yet that contains a fix for the issue. You can workaround this my manually triggering a Maven -> package
build from within Eclipse or by installing the latest snapshot of the Maven Integration for Eclipse (as described in the issue).
Published by martinlippert almost 2 years ago
Preferences -> Extensions -> Spring Boot Tools -> Open Rewrite
(in VSCode) or Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Server -> Open Rewrite
(in Eclipse).Published by martinlippert almost 2 years ago
Published by martinlippert almost 2 years ago
Published by martinlippert about 2 years ago
Preferences -> Installation Details
and uninstall the following features via the Uninstall
button, then restart the IDE, do a Check 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
Ansi Console
anymore. If you upgrade an existing installation, please uninstall this extension prior or after upgrading Spring Tools 4 for Eclipse.Published by martinlippert about 2 years ago
pom.xml
file with Open With
and select the Generic Editor
.Published by martinlippert about 2 years ago
Not properly disposed SWT resource
was caused Spring Starter Project (#797)pom.xml
file with Open With
and select the Generic Editor
.Published by martinlippert over 2 years ago
pom.xml
file with Open With
and select the Generic Editor
.Published by martinlippert over 2 years ago
pom.xml
file with Open With
and select the Generic Editor
.Published by martinlippert over 2 years ago
startupSnapshot
instead of startup
timer call to avoid wiping out the underlying data(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.
Published by martinlippert over 2 years ago
(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.
Published by martinlippert over 2 years ago
(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 select Use 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.
Published by martinlippert almost 3 years ago
(Eclipse): Updates from STS <= 4.12.1 to the latest Eclipse 2021-1 release will not work due to an incompatibility between the slightly outdated m2e.egit integration that was part of STS <= 4.12.1 distributions and the newest EGit version that is included in Eclipse 2021-12. Therefore the automatic update will only update the Spring Tools components from 4.12.1 to 4.13.0, without also updating the underlying Eclipse release. If you want to updat the underlying Eclipse release as well, please uninstall the m2e.egit integration feature as a first step using the About
dialog, then Installation Details
, select the Maven SCM Handler for EGit
feature and uninstall it. After that, updates to the latest Eclipse platform should work again.
(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 select Use 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.
Published by martinlippert almost 3 years ago
This is an update release for the Eclipse-based distributions only. The VSCode and Theia extensions remain unchanged.
Preferences -> General -> Web Browser
and then select Use External Web Browser
.Published by martinlippert about 3 years ago
Preferences -> General -> Web Browser
and then select Use External Web Browser
.