Chapter 3. Issues

3.1. Resolved Issues for Red Hat CodeReady Studio
Copiar o link

To view information about resolved issues in this release of CodeReady Studio, see the Resolved Issues.

To view information about known issues in this release of CodeReady Studio, see the Known Issues.

The following known issues are highlighted:

JBDS-4710: Central page is not showing proper content after page reload
JBIDE-26118: Cannot Create JSF2 Composite component from current selected source
JBIDE-26549: Projects from Red Hat Central are containing errors in it (removed package in java 11)
JBIDE-26602: Switching JDKs for EAP7.2 breaks EAP Launch configuration
JBIDE-26569: Cannot create hibernate config file for hibernate 5.3 and 5.4
JBIDE-26480: Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio
JBIDE-26604: Cannot connect to JMX server connection with EAP 7.1 remote local system on Java 8
JBIDE-26639: Connect wizard (macOS): have to repeatedly allow the security certificate for open.paas.redhat.com

Following is a list of issues for the CodeReady Studio and Fuse integration:

FUSETOOLS-2859: For a project that contains a data transformation file, if you change the Camel version from a version earlier than 2.20 to version 2.20 or later, you must open the data transformation file in the Data Transformation editor to complete the Camel version change. Otherwise, the project creates an error at runtime.
FUSETOOLS-3244: Fuse Online Integration projects require Maven that is lower than 3.6.

You must provide a Maven version that is lower than 3.6 before you can create a Fuse Integration project:

On your local machine, install a Maven version that is lower than 3.6. For details, see Downloading Apache Maven
In CodeReady Studio, select Window Preferences Maven Installations and then add your local Maven installation that is less than version 3.6.
Verify that your locally installed Maven version is the default.