All notable changes to the Liberty Tools extension will be documented below.
Version 24.0.3 of Liberty Tools for Visual Studio Code is a fix release that contains minor enhancements and fixes. Version 24.0.3 requires Visual Studio Code version 1.78+ and requires Java 17 or later.
Notable changes:
- Updated Eclipse LSP4Jakarta version to 0.2.1 to resolve bug where Jakarta EE diagnostics were not appearing.
- OpenLiberty#322
- For more information regarding changes for version 0.2.1, refer to the release notes: https://github.com/eclipse/lsp4jakarta/releases/tag/0.2.1
- Added instructions for when the Liberty dashboard detects no Liberty projects.
See the commit log for the full set of changes since the previous release.
Version 23.0.12 of Liberty Tools for Visual Studio Code contains enhancements for editing support. Version 23.0.12 requires Visual Studio Code version 1.78+ and requires Java 17 or later.
NOTE: There is a known problem with Jakarta EE diagnostics in this release. For details on the issue and the workaround, please refer to issue #322. For more known problems and workarounds for this release, please refer to the wiki: https://github.com/OpenLiberty/liberty-tools-vscode/wiki/Known-Problems-and-Limitations.
Notable changes:
- Updated Liberty Config Language Server version to 2.1.1. For information regarding changes for version 2.1, refer to the release notes linked below:
- Updated Eclipse LSP4Jakarta version to 0.2.0. For more information regarding changes for version 0.2.0, refer to the release notes linked below:
See the commit log for the full set of changes since the previous release.
Version 23.0.9 of Liberty Tools for Visual Studio Code is a fix release that contains minor enhancements and fixes. Version 23.0.9 requires Visual Studio Code version 1.78+ and requires Java 17 or later.
Notable changes:
- Updated Liberty Config Language Server version to 2.0.1. For information regarding changes for version 2.0.1, refer to the release notes linked below:
- Bug fix for “Start in container” action not appearing when project parent folder is opened in VS Code Explorer - OpenLiberty#258
- Bug fix for the Liberty Dashboard not refreshing project names after they are changed - OpenLiberty#177
- Bug fix for parameter field in “Start…” command redirecting focus to the terminal - OpenLiberty#210
- Added the build file path as a tooltip when hovering over project names in the Liberty dashboard - OpenLiberty#208
See the commit log for the full set of changes since the previous release.
Version 23.0.6 of Liberty Tools for Visual Studio Code contains minor enhancements and fixes. Version 23.0.6 requires Visual Studio Code version 1.78+ and requires Java 17 or later.
Notable enhancements:
- Update to allow context aware snippets in Java files provided by Eclipse LSP4Jakarta, Language Server for Jakarta EE.
- Update to latest version of
vscode-languageclientto resolve language client failures
See the commit log for the full set of changes since the previous release.
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.homesetting 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.M1or higher) - Start/Stop dev mode
- Start dev mode with custom parameters
- Run tests
- View unit and integration test reports