Skip to content

Known Problems and Limitations

Jump to bottom
Trevor Crawford edited this page Oct 18, 2024 · 15 revisions

Version 24.0.9 and older

Problem/Limitation Workaround
Multi-module projects are not explicitly supported. The following link is for one known issue, but other undiscovered problems might exist: #555 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-intellij/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 <path-to-aggregator-pom.xml> -am -pl :<root-module-name>
Some developers may run into exceptions when running the “Run tests” action. For more information on the bug, refer to this issue: https://github.com/OpenLiberty/liberty-tools-intellij/issues/976. These exceptions may result in a failure to generate test reports. The exceptions happen due to a bug with the maven-surefire-report-plugin version 3.5.0. A fix is available in version 3.5.1. For more information please refer the following ticket: https://issues.apache.org/jira/browse/SUREFIRE-2257. To ensure you are using version 3.5.1 (or a version below 3.5.0), you need to add the maven-surefire-report-plugin to your project’s pom.xml to force Maven to download the version you specify. For example: 
<plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-surefire-report-plugin</artifactId>
 <version>3.5.1</version>
</plugin>
You might have trouble connecting the debugger to the Liberty runtime when you customize the Liberty install location in the build file. For example, if you use Maven and your pom.xml file contains a value like /Users/.../singleModMavenMP/myinstalldir/wlp for the <installDirectory> property, then Liberty is installed in the specified directory and the IDE debugger might not connect. Remove the configuration that specifies the custom location while you are debugging. You can restore this customization after debugging is complete.
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 IntelliJ 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. It is possible you may receive a "No documentation found" message on hover. If observed, please report your experience on this GitHub issue: #687. No workaround available.
rest_get and mpirc completion options may appear when you trigger completion (ctrl/cmd + space) in a Java file outside of a class, where they are not applicable. You can ignore these suggestions when the cursor is not inside a class.
When you trigger completion (ctrl/cmd + space) in the featureManager section of the server.xml, and there is no prompt text already (e.g. <feature></feature>), all the features are listed, including some features with incompatible version numbers. If you subsequently type letters to filter the list, these incompatible version features may appear more prominently. If you type letters before triggering completion (ctrl/cmd + space), the expected filtering occurs and no features with incompatible version numbers will show.
Diagnostics or quick fixes for Jakarta EE or MicroProfile might not be published when a file is opened and diagnostics or quick fixes should be provided. If observed, please report your experience on this GitHub issue: #648 You can try editing the file to see if diagnostics and quick fixes appear. You can also try closing and reopening the file.

Version 24.0.6 and older

Problem/Limitation Workaround
While editing a file, the underline associated with a warning or error diagnostic might occasionally appear out of sync with your code. diagnostic underline out of sync with code If you encounter this problem, click on a different window and then return to IntelliJ. The diagnostics are refreshed.
Some diagnostic messages have associated quick fixes that on occasion fail to appear in the IDE. This problem can happen after you close all files and reopen a file of interest. Exit the IDE and restart to reactivate quick fixes.
rest_get and mpirc completion options always appear when you trigger completion (ctrl/cmd + space) in a Java file. You can ignore these suggestions when the cursor is not inside a class.
When you use a Gradle project with a space in the name (e.g. "my app") then Liberty Start does not work. Remove the space from the project name.

Version 24.0.3 and older

Problem/Limitation Workaround
When you run an action from the Liberty dashboard, the focus is not automatically pulled to the corresponding terminal window. For example, you might get confused if you are working in the Liberty terminal and then open a new terminal tab. If you execute an action from the Liberty dashboard, the action executes in the Liberty terminal tab, but the terminal window focus is now on the new terminal tab. Therefore, you might not see the action executing and wonder whether something went wrong. To monitor the Liberty terminal, you might need to click it to give it focus before (or after) you execute the Liberty action.
Clone this wiki locally