Chapter 5. Known issues

JBIDE-27591: Hot deploy does not work with OpenShift server adapter.

To work around this issue, go to OpenShift Server Adapter Settings and uncheck the Use inferred Pod Deployment Path checkbox. Set the Pod Deployment Path field to /opt/eap/standalone/deployments/.

JBDS-4710: Central page is not showing proper content after page reload.

To work around this issue, reopen Red Hat central.

JBIDE-27066: Cannot login to OpenShift 4.4.0 cluster using jdk11.

To work around this issue, use the JDK version 8 or configure Java to use TLSv1.2 as your SSL protocol.

To configure Java to use TLSv1.2, open the file codereadystudio.ini located in the studio directory inside of the CodeReady Studio installation directory.

Add the following line under the -vmargs section:

-Djdk.tls.client.protocols=TLSv1.2

-Djdk.tls.client.protocols=TLSv1.2

JBIDE-27605: Conflicting dependency when updating from BYOE 2020-09 + JBT 4.17.0.Final to JBT 4.18.0.Final.

To work around this issue, use Help Install New Software, select the Jbosstools stable update site and select both JAX-RS and JAX-WS features. Both features will be updated.

Alternatively, use Preferences Install/Update Available Software and disable the latest Eclipse release. As a result, Eclipse 2020.12 is installed.

FUSETOOLS-3373: Fuse Integration Project is created with error for camel version Fuse 7.2 and 7.1.

To work around this issue, add the following lines to the jakarta.xml.bind-api file to define the jakarta version:

<dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<version>2.3.3</version>
</dependency>

<dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<version>2.3.3</version>
</dependency>

The latest available version is 2.3.3. For further information on the latest version, see Maven Repository: Jakarta XML Binding API.