sts4 | next generation of tooling for Spring Boot | Code Editor library

Thanks for bringing this issue to my attention. I am not subscribed to the AJDT and AspectJ Bugzilla projects, i.e. I only noticed that something is wrong today when reading this question.

Deleted the project (only from eclipse, don't check to option to delete from disk). Then reimport in workspace solved the problem.

After reading some documentation, I found that you need Eclipse for Enterprise Java Development. So just installing this plugin solved the problem:

There is no code coverage feature installed by default in the Spring Tools 4 for Eclipse distribution (and never was, as far as I remember), but you might have had an Eclipse installation with such a third-party plugin installed. Maybe installing this from the marketplace helps:

marketplace.eclipse.org/content/eclemma-java-code-coverage

The branding feature is nothing that you should install into an existing Eclipse installation. It provides the product branding for the Spring Tools 4 distribution and does not provide any functionality beyond that.

If you want to install the Spring Tools 4 into an existing Eclipse installation, you can:

• use the Eclipse Marketplace entry for Spring Tools 4
• or install from the p2 repository by selecting the features you want to instal manually (as described here: https://github.com/spring-projects/sts4/wiki/Installation#install-spring-tools-4-into-an-existing-eclipse-via-a-p2-repo)

Another way would be to download the ready-to-use distribution from https://spring.io/tools, which comes with the latest Eclipse release included and Spring Tools 4 pre-installed.

Or is it still something from STS3

Short answer: it belongs to STS 4 and should not be removed when migrating from STS 3 to STS 4.

Longer answer:

That particular builder runs 'validation checks' that are specific to STS 4 and are run inside of an Eclipse builder.

However, there is currently only one validation rule defined in that builder. This rule checks for use of @ConfigurationProperties annotation and recommends to add the corresponding annotation processor to the classpath if it is not already there.

Disabling or removing the builder will have no other ill-effects except for disabling that single validation check. So if you do not use Spring Boot @ConfigurationProperties then it will not affect you at all. Even if you do use it (now or in the future), the impact is marginal. Basically, you will have to remember to add the annotation processor dependency yourself manually but won't get a reminder in the form of warning in the editor.

Moving forward, this builder is probably going to be phased out and removed in the future. Newer validations, such as the validation of 'SpEL' expression being implemented more recently, are now being defined in the language server rather than in the Eclipse builder. If we can re-implement the @ConfigurationProperties check in the language server, then it would make sense to get rid of the Eclipse validation builder completely as it would no longer serve a purpose.

So to be totally clear, yes it is part of STS 4, and still doing something useful (in Eclipse), but it predates the adoption of language servers as means to implement things like validations in a way that is not Eclipse-specific.

It depends on your Random Access Memory (RAM) of system.

As per your current sts.ini file,

-Xms256m

-Xmx1024m

which is generally set for 2GB RAM of system.

If you have more than 2GB RAM, for example 4GB RAM, please set:

-Xms512m

-Xmx2048m

Above settings indicates STS will occupy upto 2GB of your 4GB RAM of system, among all other open applications .

Thanks and Regards.

Adding the -vm arg to the .ini file should work, but you need to carefully put that into the right place inside of that file. -vm has to be the first line in that file, followed by an additional like pointing to the java executable of the JDK. Then the third line should proceed with the -startup part that you have in your .ini file.

I couldn't get it to work with HtmlUnit, but got the expected result using Selenium, in case someone else is interested in this feature: