22.1 Known Issues

General known issues

Symptom	Workaround
When using the Docker Tooling perspective to pull an image, you may encounter the following error: org.mandas.docker.client.exceptions.DockerException: java.io.IOException: Cannot run program "docker-credential-desktop": error=2, No such file or directory.	To workaround this issue, go to ~/.docker/config.json and change credsStore to credStore. You may also use docker pull manually to pull down the image you need rather than using the tooling. Issue raised here.
There is no warning provided if you try and use incompatible features in a Liberty server, e.g. servlet-3.0 and servlet-3.1 in server.xml	Remove the incompatible feature
During a gradle build you receive java.lang.IllegalArgumentException: Unsupported class file major version 61. Issue raised against eclipse as they do not ship a Java 17 compatible version of the Gradle Tooling api (issue here).	Set system property GRADLE_VERSION_OVERRIDE and WDT will use that value instead of the one the gradle plugin says to use. This only works if code requesting the gradle version is WDT, if it's a plugin (e.g. liberty gradle plugin) this workaround won't help.
When creating or importing a project which uses the Liberty Gradle plugin version 3.x, no prompt appears to create a runtime and server for the project.	This can be worked around by manually specifying the location of the server.xml in the build.gradle file which is detailed in this issue.
When generating a web service into an OSGi app and completing the wizard, a dialog appears saying that the app hasn't started successfully. At this point, the liberty server logs report: The application JWS_OSGi_BU.app could not be started as it could not be found at location JWS_OSGi_BU.app.eba.	Clicking "Finish" again deploys the app and the wizard completes successfully.
When creating and deploying a web service client using the Generate Web Service wizard, Eclipse may wrongly report that the generated client has validation errors and may not deploy correctly.	In this case, try clicking OK to continue with the deployment. Once the wizard has completed, check for error markers on the web service client project.

• Aesthetic inconsistencies present in some wizards when using dark mode

Jakarta EE9 specific known issues

Symptom	Workaround
WDT allows a user to select the Dynamic Web Project facet v5.0. This version of the facet uses Jakarta EE9 and WDT does not support Jakarta EE9. An update to WTP has made this available however WDT does not yet support this.	Jakarta EE9 and Dynamic Web Project facet v5.0 are not supported at this time