-
Notifications
You must be signed in to change notification settings - Fork 26
Known Problems and Limitations
Trevor Crawford edited this page Jun 30, 2023
·
19 revisions
Problem/Limitation | Workaround |
---|---|
Multi-module projects are not explicitly supported. | 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 |
While editing a file, the underline associated with a warning or error diagnostic may occasionally appear out of sync with your code. | If this becomes a problem simply click on a different window and then return to IntelliJ. The diagnostics should be refreshed. |
Some diagnostic messages have associated quick fixes which on occasion fail to appear in the IDE. This can happen after you close all files and reopen a file of interest. | You must exit the IDE and restart in order to reactivate quick fixes. |
When you run an action from the Liberty dashboard, the focus is not automatically pulled to the corresponding terminal window. For example, if you open a new terminal window in the IDE which covers the Liberty terminal and then execute an action from the Liberty dashboard, the action will execute in the correct terminal, but that window will not show over the new terminal you opened. | To monitor the Liberty terminal you may need manually to click on it to give it focus before (or after) you execute the Liberty action. |
You may have trouble connecting the debugger to the Liberty runtime when you customize the Liberty install location in the build file. For instance, if you use Maven and your pom.xml contains a value like /Users/.../singleModMavenMP/myinstalldir/wlp for the <installDirectory> property, then Liberty will be installed in the specified directory and the IDE debugger may not connect. |
While debugging, you need to remove the configuration which specifies the custom location. This customization can be restored once debugging is complete. |