In STS 3.6.4 we introduced “.properties” editor support, for editing Spring Boot configuration properties.

Soon thereafter, people started asking about support for “.yml” files as well. We are proud to say that the “.yml” support is now reality.

Check out the 5 minute video demo to see this in action:

The Spring Boot Yaml editor is built on top of YEdit. STS adds boot-specific content-assist, validation, hover-infos and hyperlink detectors.

It can be tried out today from STS’s nightly update site and is planned to be released as part of STS 3.7.0 near the end of June 2015.

Spring Boot STS Tutorial

Spring Tool Suite 3.6.4 was just released last week. This blog post is a tutorial demonstrating some of the new features STS provides to create and work with Spring Boot applications.

In this tutorial you’ll learn how to:

• create a Simple Spring Boot Application with STS
• launch and debug your boot application from STS
• use the new STS Properties editor to edit configuration properties.
• use @ConfigurationProperties in your code to get the same editor support for your own configuration properties.

Are you an Eclipse user? Do you want a fast and easy way to search for text snippets and patterns in your workspace? Then read on!

A new “Quick Search” is included in Spring ToolSuite (STS) 3.3.0 and Groovy Gails Tool Suite (GGTS) 3.3.0 which have just been released. Even if you are not a Spring or Grails developer, you might be interested in this Feature because it can also be installed separately into a vanilla Eclipse.

Introducing the Quick Search Dialog

You open the dialog by pressing CTRL+SHIFT+L (or CMD+SHIFT+L on Mac):

Scripted, a JavaScript editor from VMWare was announced on this blog last month. In this article we’ll take a look under the hood at Scripted’s Dependency Analysis Engine. But before diving into the details, lets motivate why we need it.

Main Motivation: Cross-file Content Assist

[caption id=“attachment_12178” align=“aligncenter” width=“533” caption=“Cross-file Content Assist”][/caption]

Two components work together to achieve this goal:

• a fine-grained type inference analysis engine


• a coarse-grained dependency analysis engine