Spring Team
Martin Lippert

Martin Lippert

Developer Tools Engineering, Spring Tool Suite Lead

Hamburg, Germany

Martin leads the Spring Tool Suite and the Spring IDE projects at Pivotal and works together with the tools team on providing the best developer tools out there for Spring and Cloud Foundry. In addition to that he works on next generation developer tooling and innovative new architectures for cloud-based developer tooling. Before joining the Spring family at Pivotal, Martin co-founded it-agile, a leading consulting and development company focused on agile software development.
Blog Posts by Martin Lippert

Spring Tools 4 - public beta released

spring tools 4

Beginning today, we enter a new chapter in the tooling landscape for Spring and the development of enterprise applications built on top of the de-facto standard, Spring Boot. By unveiling the public beta of the next generation of our Spring tooling, we allow developers around the globe to get a preview of what is coming next to improve their developer experience around Spring and Spring Boot.

Spring Aware

smart code completion

The all-new Spring Tools 4 analyze your projects on the fly, understand the Spring constructs inside, and provide easy and super quick navigation to all your Spring elements. Finding a specific request mapping, an exact bean definition, or a newly created function was never as easy as with the new Spring Tools 4.

Read more...

Spring Tool Suite 3.9.1 released

I am happy to announce the 3.9.1 release of the Spring Tool Suite, our Eclipse-based tooling.

Highlights from this release include:

  • updated to Eclipse Oxygen.1a release (https://www.eclipse.org/oxygen/noteworthy/)
  • includes support for JDK9 and JUnit 5 (https://www.eclipse.org/eclipse/news/4.7.1a/)
  • updated Spring Cloud CLI integration (switch to on-demand install)
  • experimental boot dashboard extension to inspect beans of running boot apps
  • refactoring support to convert application.properties to application.yml
  • a number of important bug fixes (organize imports shortcut is back, for example)
Read more...

How to get STS/Eclipse running on macOS High Sierra (10.13)

The new version of macOS called High Sierra (10.13) will soon go GA and we expect many of our STS/Eclipse users and Spring developers will upgrade their machines sooner than later. In case you have your system running with an English locale, you are fine and everything will be good.

If you are running your system with a different language configured, you will see all menu items of Eclipse or STS being disabled after the upgrade to macOS High Sierra.

The good news is: you can quickly get this fixed without waiting for an update of Eclipse or STS. Go into the Eclipse.app or STS.app package, move into the “Contents” folder, and edit the Info.plist file (with a text editor of your choice). Scroll down to the list of locales and remove everything from that list except for the “en” entry. Save the file, exit your text editor, and you are good again.

Read more...

Spring Tool Suite 3.9.0 released

Dear Spring Community,

I am happy to announce the 3.9.0 release of the Spring Tool Suite, our Eclipse-based tooling.

Highlights from this release include:

  • updated to Eclipse Oxygen release (Oxygen New and Noteworthy)
  • improved support for editing cloud foundry manifest files
  • improved support for using Spring Cloud CLI services (incl. log streaming to console view)

To download the distributions, please go visit:

Detailed new and noteworthy notes can be found here: STS 3.9.0 New & Noteworthy.

Read more...

New beta versions of Concourse pipeline and Cloud Foundry manifest editing support released for Visual Studio Code

Back in February 2017 we started to introduce new IDE-agnostic tooling support with our first beta version of the Cloud Foundry manifest editing support. As promised, we continue this journey with an improved version of the Cloud Foundry manifest editing support for Visual Studio Code and brand-new support for editing Concourse task and pipeline definitions - also as an extension to Visual Studio Code. This marks our second step towards implementing tooling in an IDE-agnostic way, adopting the language server protocol from Visual Studio Code.

Read more...

Spring Tool Suite 3.8.4 released

Dear Spring Community,

I am happy to announce the 3.8.4 release of the Spring Tool Suite, our Eclipse-based tooling.

Highlights from this release include:

  • updated to Eclipse Neon.3
  • completely revamped wizard for direct access to start.spring.io
  • boot dashboard: support for local Spring Cloud CLI services
  • boot dashboard: support for routes when deploying apps to CF
  • fixed font rendering on main STS dashboard
  • added support for Buildship 2.0
  • improved reliability for boot dashboard when showing status of running boot apps
  • issue tracking moved to GitHub Issues
Read more...

Cloud Foundry Manifest Editor Beta released for Visual Studio Code

As part of our activities to support developers around the globe building applications with Spring and deploying those apps to Cloud Foundry and PCF, we are proud to announce our first beta version of the Cloud Foundry Manifest editing support for Visual Studio Code (on macOS, Linux x64, and Windows).

Why Visual Studio Code?

Visual Studio Code is a lightweight and open-source code editor that runs on macOS, Linux x64, and Windows. It is based on an interesting architecture with regards to extensibility. Support for languages in Visual Studio Code gets implemented as so called “language servers”. Those language servers are independent of the editor that you use. The editor and the language server are connected using a protocol (called the language server protocol). Even though Visual Studio Code introduced this protocol, other editors and IDEs started to adopt this language server protocol - like the Eclipse IDE (from version 4.7 on) or Eclipse Che as a cloud IDE. Other lightweight editors like Sublime Text and Atom will likely offer support in the near future, too. As a result, we can focus on implementing the Cloud Foundry manifest editor support as an independent language server and you can add this support to the editor or IDE of your choice.

Read more...

Spring Tool Suite 3.8.3 released

Dear Spring Community,

I am happy to announce the 3.8.3 release of the Spring Tool Suite, our Eclipse-based tooling.

STS 3.8.3 focuses on adopting Eclipse Neon.2 and fixing existing issues. The list of changes include:

  • Updated to Eclipse Neon.2
  • Added support for one-time passcode for Cloud Foundry targets in the Spring Boot Dashboard
  • Added support for WAR packaging of Spring Boot apps when deploying them to CF in the Spring Boot Dashboard
  • Added support for health-check in Cloud Foundry manifest files
  • Fixed a number of most-reported errors from the automated error reporting
  • and more...
Read more...

Spring Tool Suite 3.8.2 released

Dear Spring Community,

I am happy to announce the 3.8.2 release of the Spring Tool Suite, our Eclipse-based tooling.

STS 3.8.2 focuses on adopting Eclipse Neon.1 and fixing existing issues. The list of changes include:

  • Updated to Eclipse Neon.1
  • Includes Eclipse Automatic Error Reporting
  • Custom Spring Initializr now usable directly from within STS
  • New Spring Starter Wizard now features default selections
  • Fixed a problem that caused parallel push of multiple apps in boot dashboard to fail
  • Fixed a deadlock when selecting BuildShip in New Spring Starter wizard
  • and more...
Read more...

Spring Tool Suite 3.8.1 released

Dear Spring Community,

I am happy to announce the 3.8.1 release of the Spring Tool Suite, our Eclipse-based tooling.

STS 3.8.1 focuses on fixing existing issues. The list of fixed issues include:

  • Spring Boot Dashboard works behind a proxy again
  • Assert templates now use JUnit or AssertJ, depending on what is on the classpath of the project
  • Fixed an issue with the Groovy-Eclipse m2e connector with missing source folders
  • Added an action to jump to the ngrok admin web UI directly from the boot dashboard
  • Fixed an issue with the port of a boot app not showing up in the dashboard
  • and more...
Read more...