Release Notes

Red Hat CodeReady Studio 12.21

Highlighted features in 12.21

Eva-Lotte Gebhardt

Levi Valeeva

Yana Hontyk

Red Hat Developer Group Documentation Team

Abstract

The Release Notes provide a brief description of the improvements, additions that have been implemented in Red Hat CodeReady Studio 12.21, and document known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.

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.21 is an update of Red Hat CodeReady Studio 12.19.1.

The following chapters describe improvements and additions implemented in Red Hat CodeReady Studio 12.21 and documents known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.

CodeReady Studio 12.21 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.5 runtime provider contains Hibernate Core 5.5.7.Final and Hibernate Tools 5.5.7.Final.

    For further information, see the Hibernate ORM 5.5.7.Final Release Notes.

  • The Hibernate 5.3 runtime provider contains Hibernate Core 5.3.22.Final and Hibernate Tools 5.3.22.Final.

    For further information, see the Hibernate ORM 5.3.22.Final Release Notes.

  • CodeReady Studio works with Red Hat JBoss Wildfly 25.

    For more information, see the WildFly Homepage.

  • CodeReady Studio tools support Java17. (JBDS-5023)

  • OpenShift Enhancements in CodeReady Studio:

    • OpenShift tools are based on odo 2.3. (JBIDE-27985)
    • The odo-based explorer supports proxies. (JBIDE-27084)
      To enable odo proxy support, set the HTTPS_PROXY environment variable when launching odo.
    • Odo supports creating operator backend services. (JBIDE-27979)

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: The Red Hat Central page is not showing content properly after page reload.

    To work around this issue, reopen Red Hat Central.

  • JBIDE-26118: Unable to create Jakarka Server Faces composite component from current selected source.
  • JBDS-4818: The CRS installer is not signed for MacOS.

  • JBDS-5032: CodeReady Studio can’t be started after installation of all software from Red Hat Central.

    To work around this issue, install a missing Mylyn bundle from the command line by running: 

    ./codereadystudio -consoleLog -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/releases/2020-12 -installIUs com.sun.xml.bind/2.2.0.v20201118-1845

    Then restart CodeReady Studio with the -clean option.

  • JBIDE-28000: App Transport Security blocks Web Browser and Web Management Console options in the Show In context menu of the server.

    To work around this issue, open the Codereadystudio.app/Contents/Eclipse/Info.plist file within the application bundle and add the following lines to the end of the file: 

    <key>NSAppTransportSecurity</key>
<dict>
    <key>NSExceptionDomains</key>
    <dict>
        <key>localhost</key>
        <dict>
            <key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
            <true/>
        </dict>
    </dict>
  </dict>
</dict>

  • JBIDE-28007: Logging into developer sandbox does not work under MacOS.

    To work around this issue, open the Codereadystudio.app/Contents/Eclipse/Info.plist file within the application bundle and add the following lines to the end of the file: 

    <key>NSAppTransportSecurity</key>
<dict>
    <key>NSExceptionDomains</key>
    <dict>
        <key>localhost</key>
        <dict>
            <key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
            <true/>
        </dict>
    </dict>
  </dict>
</dict>

  • Target platform and installer known issues in CodeReady Studio:

    • 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, click Help → Install New Software, select the Jbosstools stable update site, and select both Jakarta RESTful Web Services and Jakarta Enterprise Web Services. Both feaures will be updated.

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

  • OpenShift known issues in CodeReady Studio:

    • JBIDE-27066: Unable to login to OpenShift 4.4.0 cluster using JDK11.

      To work around this issue, use the JDK 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

  • Webservices known issues in CodeReady Studio:

    • JBIDE-27743: Unable to create Web Service client from wsdl definition using Wildfly 22 and Apache CXF 3.3.5+.

      To work around this issue, use Apache Axis or JBossWS instead of CXF runtime to continue your service client definition.
      Alternatively, update and export the order of your source folder so that your source folder appears first. To do so, use the following path: Dyn. Web Project → Properties → Java Build Path → Order.

    • JBIDE-27744: WS Tester does not allow POST request due to low size of DH key.
    • JBIDE-27781: NPE occurs during deletion of Dynamic Web Project with generated web.xml descriptor.
    • JBIDE-27842: WS Tester Jakarta Enterprise Web Services invocation for local wsdl results in error message Provider org.apache.axis2.jaxws.spi.Provider not found.

  • Code Ready Containers known issues in CodeReady Studio:

    • JBIDE-27741: CRC does not start properly and results in error message Unable to execute request to request url https://api.crc.testing:6443/.well-known/oauth-authorization-server.

    • JBIDE-27921: CRC 1.28.0 setup on Windows and MacOS does not provide bin/oc anymore and prevents CRC tooling to start.

      To work around this issue, go to the CRC home folder and create a bin directory.

  • Fuse Integration Project known issues in CodeReady Studio:

    • FUSETOOLS-3337: Unable to deploy Fuse project with DataTransformation to Fuse on Karaf 7.x runtime.

    • FUSETOOLS-3373: Fuse Integration Project created with an error for Camel 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.

Legal Notice

Copyright © 2021 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.