Release Notes

Red Hat CodeReady Studio 12.16

Highlighted features in 12.16

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.16 and document known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.

1. About this release

Red Hat CodeReady Studio 12.16 is an update of Red Hat CodeReady Studio 12.15.

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

CodeReady Studio 12.16 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.

2. Enhancements

3. Bug fixes

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

4. Deprecated functionality

  • JBIDE-27317:Android Development Tools are no longer supported.
  • JBIDE-26987: Visual Page Editor, Forge Tools and JST Server Adapters are no longer fully supported.

5. Known issues

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

The following known issues are highlighted:

  • JBIDE-27066: Cannot login to OpenShift 4.4.0 cluster.

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

    To configure Java to use TLSv1.2, use: 

    $ java -Djdk.tls.client.protocols=TLSv1.2 MyApplication.jar

    Replace MyApplication with the name of the application.

  • JBIDE-27322: Unable to restart Eclipse after installing updates from JBoss or Red Hat Developer Portal.

    To work around this issue, use JDK 11.

  • JBIDE-26602 EAP 7.2 server fails to start after switching between JDKs.

  • JBIDE-26445: Remote EAP 7.x server adapter fails to start on Windows when connected via local remote system type with an error message: 

    cmd' is not recognized as an internal or external command, operable program or batch file
  • JBIDE-26600: Cannot remove JSF capabilities from JSF project.
  • JBIDE-26118: Cannot Create JSF2 Composite component from current selected source.

Legal Notice

Copyright © 2020 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.