Known Problems and Limitations
| Problem/Limitation | Workaround |
|---|---|
| Multi-module projects are not explicitly supported. Two known issues are linked below, however, there may be other undiscovered problems: 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 |
| If more than one project open in the VS Code Explorer has the same app name, snippets will not be provided by the language servers. | Rename the applications so they do not share the same app name. There are some common ways for defining project names. For Maven, use the <finalName> property under the <build> section of the pom.xml. For Gradle, use the rootProject.name property in settings.gradle. |
Completion suggestions sometimes missing for Liberty features in server.xml. Suggestions that begin with 'abc' are words from the current file.
|
To avoid this, type ctrl + space to pull up Liberty feature suggestions before typing any characters between the <feature></feature> tags. If you do hit this issue, you can exit to another window and then come back to VS Code and type ctrl + space. The Liberty feature suggestions should then be available. |
| Depending on where dev mode is in its process of starting up, you may have trouble stopping dev mode using the Liberty Stop action. | Click in the terminal instance in VS Code and type ctrl + c. This should end the dev mode instance. |
| 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. This will enable the Liberty Start in container action to be available. 
|