Highlighted features in 12.19
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. About this release
Red Hat CodeReady Studio 12.19 is an update of Red Hat CodeReady Studio 12.18.
The following section describes improvements and additions implemented in Red Hat CodeReady Studio 12.19 and documents known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.
CodeReady Studio 12.19 is available from a number of sources. For more information on how to set up CodeReady Studio, see the Installation guide.
For more information about operating systems, chip architectures, and Java Development Kits (JDK) supported by this release, see the Supported Configurations and Components page.
Chapter 2. Enhancements
The Hibernate 5.4 runtime provider now contains Hibernate Core version 5.4.30.Final and Hibernate Tools version 5.4.30.Final.
For further information, see the Hibernate ORM 5.4.30.Final Release Notes.
CodeReady Studio now supports Red Hat JBoss Wildfly 23.
For more information, see the WildFly Homepage.
CodeReady Studio is now compatible with JBoss EAP 7.4.Beta.
For more information, see the Red Hat JBoss Enterprise Application Platform 7.4.0 Beta Release Notes.
OpenShift Enhancements in CodeReady Studio:
OpenShift tools are now based on
odo 2.0.7. (JBIDE-27719)
- It is now possible to bootstrap and login to a Developer Sandbox using OpenShift tools. (JBIDE-27680)
- It is now possible to add, remove, and edit devfile registries in OpenShift tools. (JBIDE-27611)
CodeReady Studio now supports Python components. (JBIDE-27612)
With this release, it is now possible to debug Python-based components using the Eclipse debugger.
- OpenShift tools are now based on
- In CodeReady Studio it is now possible to add environment variables to the configurations of your Quarkus Applications. (JBIDE-27738)
Chapter 3. Bug fixes
- To view information about resolved issues in this release of CodeReady Studio, see Resolved Issues.
Chapter 4. Deprecated functionality
With this release, there are no deprecated functionalities.
Chapter 5. Known issues
To view information about known issues in this release of CodeReady Studio, see Known Issues.
The following known issues are highlighted:
- JBIDE-27796: BYOE does not install Oauth UI needed by devsandbox.
- JBIDE-27789: BYOE does not install Quarkus.
- JBIDE-27737: CRC Hangs on Starting status in some situations on Windows.
JBIDE-27741: Failed to refresh element Unable to execute request to request url
JBIDE-27787: Problems occurred while performing installation: No repository found at
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
JBDS-4710: Central page is not showing proper content after page reload.
To work around this issue, reopen Red Hat central.
- JBIDE-26118: Cannot Create JSF2 Composite component from current selected source.
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.inilocated in the studio directory inside of the CodeReady Studio installation directory.
Add the following line under the -vmargs section:
- JBDS-4818: Monitor binary signing policy in mac os platforms.
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.
Preferences → Install/Update → Available Softwareand disable the latest Eclipse release. As a result, Eclipse 2020.12 is installed.
- JBIDE-27498: Refreshing Openshift connection does not work for started CRC 1.16 in studio when asked by warning dialog.
- FUSETOOLS-3337: Unable to deploy Fuse project with DataTransformation to Fuse on Karaf 7.x runtime.
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-apifile to define the jakarta version:
<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.