All notable changes to the Liberty Tools extension will be documented below.
Version 0.1.12 of Liberty Tools for Visual Studio Code is an early release that contains new functionality and fixes. Liberty Tools for Visual Studio Code now requires Java 17 and depends on the XML by Red Hat and Debugger for Java Visual Studio Code extensions.
Notable enhancements:
- Editing assistance (completion, hover, diagnostics and quick-fixes) when editing server.xml, server.env, and bootstrap.properties files via the Liberty Config Language Server.
- Editing assistance (code snippets, diagnostics and quick-fixes) for Jakarta EE 9.x Web Profile APIs when editing Java files via the Eclipse LSP4Jakarta, Language Server for Jakarta EE.
- Liberty projects are now automatically detected via the presence of a “src/main/liberty/config/server.xml” file.
- New “Liberty: Attach Debugger” Liberty action, accessible through the Liberty Dashboard or Visual Studio Code Command Palette. Requires “Liberty: Start” to have been run first.
- Ability to run Liberty actions through the Visual Studio Code Command Palette or the keyboard shortcut: Shift + Alt + L.
- “Liberty: Start…” saves command history.
- Ability to manually add projects to the Liberty Dashboard.
- New icons for Maven and Gradle projects in the Liberty Dashboard.
See the commit log for the full set of changes since the previous early release.
- Rename extension to Liberty Tools for VS Code
- Rename Liberty Dev Dashboard to Liberty Dashboard
- Honour Maven and Gradle wrapper settings when running dev mode
- Removed "tech preview" wording from "Start in container" action
- Added dependency on Tools for MicroProfile
- Added Start in container (tech preview) action
- Upgrade lodash dependency version
- Detect custom test report locations
- Add refresh button to Liberty Dev Dashboard
- Persist custom parameters between runs of dev mode
- Upgrade minimist and acorn dependency versions
- Support for the Liberty Gradle Plugin
- Bug fixes for Liberty Project Provider
- Updated Manifest
- Improved message when test reports do not exist
- Added OpenLiberty category to Liberty Dev commands
- Change name to Open Liberty Tools
- Enhancement to honour
java.home
setting withliberty.terminal.useJavaHome
- Bug fix to recognize plugins defined in profile section of
pom.xml
- View supported liberty-maven-plugin projects in the workspace (must be of version
3.0.M1
or higher) - Start/Stop dev mode
- Start dev mode with custom parameters
- Run tests
- View unit and integration test reports