Release Notes
Highlighted features in 12.18
Eva-Lotte Gebhardt
egebhard@redhat.com
Levi Valeeva
levi@redhat.com
Yana Hontyk
yhontyk@redhat.com
devtools-docs@redhat.com
Abstract
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.18 is an update of Red Hat CodeReady Studio 12.17.
The following section describes improvements and additions implemented in Red Hat CodeReady Studio 12.18 and documents known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.
CodeReady Studio 12.18 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
CodeReady Studio now supports Red Hat JBoss Wildfly 22.0.0.Final. (JBIDE-27494, JBIDE-27600)
For more information, see the WildFly Homepage.
CodeReady Studio is now compatible with JBoss EAP 7.3.4.
For more information, see the JBoss Enterprise Application Platform 7.3 Update 4 Release Notes.
CodeReady Studio is now compatible with JBoss EAP XP 2.0.
For more information, see Develop Eclipse MicroProfile applications on Red Hat JBoss Enterprise Application Platform XP 2.0.
OpenShift tools are now based on
odo 2.0.3
. (JBIDE-27530, JBIDE-27563, JBIDE-27553, JBIDE-27531)With this enhancement, deployment based on devfiles (developer oriented manifest files) is now supported.
The Hibernate 5.4 runtime provider has been updated to 5.4.27.Final.
For further information, see the Hibernate ORM 5.4.27 Release Notes.
The Hibernate 5.3 runtime provider has been updated to 5.3.20.Final.
For further information, see the Hibernate ORM 5.3.20 Release Notes.
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:
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.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
- JBDS-4818: Monitor binary signing policy in mac os platforms.
JBIDE-27449: Errors after creating a new Quarkus project.
To work around this issue, delete the following 2 lines from the
pom
file:<goal>prepare</goal> <goal>prepare-tests</goal>
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 will be installed.- JBIDE-27498: Refreshing Openshift connection does not work for started CRC 1.16 in studio when asked by warning dialog.
JBIDE-27496: Cannot update to JBT 4.17.0.Final from BYOE + JBT 4.16 - JAXWS conflicting dependency.
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.FUSETOOLS-3393: [regression] Camel debugger is not working with Fuse 7.8+.
To work around this issue, use the JMX navigator and connect to the starting process of the Camel project. Expand the menu and right click the Camel node. Click
Edit routes
and select your options.- 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-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>
The latest available version is 2.3.3. For further information on the latest version, see Maven Repository: Jakarta XML Binding API.