Known Problems and Limitations
| Problem/Limitation | Workaround |
|---|---|
| Multi-module projects are not explicitly supported. The following links are for two known issues, but other undiscovered problems might exist: https://github.com/OpenLiberty/liberty-tools-vscode/issues/204 https://github.com/OpenLiberty/liberty-tools-vscode/issues/251 | Some potential workarounds are commented in the linked issues. You can try to work with multi-module projects, but there is no guaranteed support. Please open any newly discovered issues here: https://github.com/OpenLiberty/liberty-tools-vscode/issues. One helpful workaround to run a multi-module project with some support is to use the Liberty Start... action and specify the following parameters: -f ../pom.xml -am -pl :<root-module-name>
|
| If more than one project open in the VS Code Explorer has the same app name, snippets are not provided by the language servers. | Rename at least one of the projects so they do not share the same app name. There are some common ways for defining project names.
|
| Depending on where dev mode is in its process of starting up, you might have trouble stopping dev mode by using the Liberty Stop action. | Click in the terminal instance in VS Code where dev mode is running and type ctrl + c. This should end the dev mode instance. |
You might observe slow performance when editing your server.xml file when invoking completion or hover. If observed, please report your experience on this GitHub issue: https://github.com/OpenLiberty/liberty-tools-vscode/issues/329
|
No workaround available. |
| Problem/Limitation | Workaround |
|---|---|
| Jakarta EE diagnostics are not appearing. | To enable Jakarta EE diagnostics, you will need to install version 1.26.0 of the Language Support for Java(TM) by Red Hat extension. You will also need to install pre-release version 0.11.2024012703 of the Tools for MicroProfile extension. For more details on how to install those versions, refer to the Workaround section in https://github.com/OpenLiberty/liberty-tools-vscode/issues/322
|
| Problem/Limitation | Workaround |
|---|---|
The Liberty Start in container action is not available when the parent folder of a Liberty project is opened in the VS Code Explorer. 
|
Open the root folder of the Liberty project directly in VS Code. Opening the root folder in VS Code makes the Liberty Start in container action available. 
|