The file within LTI had an identical path to a file with the same name in the LSP4Jakarta JDT core jar. Which properties file gets loaded at runtime is non-deterministic and can change depending on the ClassLoader used in a specific environment. When the file from LSP4Jakarta was loaded instead of the one from LTI several key/value pairs were not found in that copy of the properties file which led to the message key being reported to the user instead of the correctly formatted message. Moving the file within LTI to another (unique) location resolves this issue.
Resolves https://github.com/OpenLiberty/liberty-tools-intellij/issues/703.
The file within LTI had an identical path to a file with the same name in the LSP4Jakarta JDT core jar. Which properties file gets loaded at runtime is non-deterministic and can change depending on the
ClassLoaderused in a specific environment. When the file from LSP4Jakarta was loaded instead of the one from LTI several key/value pairs were not found in that copy of the properties file which led to the message key being reported to the user instead of the correctly formatted message. Moving the file within LTI to another (unique) location resolves this issue.