I just ran into this problem, and I have the latest (at the moment) version of Spring Tool Suite (version: 3.6.3.SR1). The solution was inspired by Kris 's comment, but instead of using a new workspace, you can βclearβ it first.
Decision
Run STS (or any other Eclipse-based IDE) with the -clean argument (which is equivalent to setting osgi.clean to "true") on the command line. Result (quote):
any cached data used by the OSGi environment and the Eclipse runtime environment will be wiped. This will clear the caches used to store the dependency resolution package and the Eclipse extension registry data. Using this option will force Eclipse to reinitialize these caches.
Example for Windows:
C:\sts-3.6.0.RELEASE\sts.exe -clean
It worked flawlessly!
Alternative solutions
If the solution above did not help, here are the main alternatives:
- creating a new workspace (as suggested by Chris)
- clean reinstall Eclipse
More detailed instructions can be found here: Keeping Eclipse Clean
source share