Interesting issue; in one of my projects, after updating the various tools I have installed, I started getting an error message indicating problems setting the project description when I’d invoke Maven -> Update Project. The error attached to this (via the Errors tab) indicated:
This talk explains the changes and restructuring the tool suite went through, and highlights new features for Spring developers. It also provides a look behind the scenes and explains the agile development process and the project rhythm of the development team behind the tool suites from SpringSource/VMware. The Eclipse Marketplace dialog appears, type Spring Tool Suite or STS into the Find textfield and hit Enter. Eclipse will send query to its server and display results as shown below: Select the version that matches your Eclipse’s version and click Install button. Here we select Spring Tool Suite (STS) for Eclipse Juno (3.8 + 4.2). Last modified: Thu Mar 18 05:09:51 UTC 2021: Last modified by: tim.lebedk. Created: Thu Mar 18 05:09:51 UTC 2021: Created by: tim.lebedk. Automated tests. SpringSource Tool Suite 2.8.1 - New and Noteworthy -!!!!! Martin Lippert 2.8.1.RELEASE November 23, 2011 Updated for 2.8.1.RELEASE. NEW AND NOTEWORTHY www.springsource.com ENHANCEMENTS – 2.8.1 General Updates Mylyn 3.6.4 The Mylyn version within STS is.
Problems encountered while setting project description.
Nature does not exist: org.springframework.ide.eclipse.core.springnature.
Check my updates … other projects … nope, looks like all the tools are up to date and other projects are working just fine. In searching online, I came across this post, which offered up a hint — but I hadn’t disabled the installation package. I’m using Spring Tool Suite version 3.6.2.RELEASE build on Eclipse Luna SR1 (4.4.1).
A friend indicated he had a similar issue a while back, and comparing the .project file in the broken project with a .project file is a working file allowed him to fix the project, so … worth a shot.
Springsource Tool Suite For Eclipse Neon
I ended up copying the buildCommand and nature sections of a working .project file into my broken project’s .project file, and all is good with the world again. Here’s the snippets I needed to paste (in the correct sections, of course):
Springsource Tool Suite
Strange issue, but … it works now, so what can I say?