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
    Copy to Clipboard Toggle word wrap
  • 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>
    Copy to Clipboard Toggle word wrap
  • 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>
    Copy to Clipboard Toggle word wrap

    The latest available version is 2.3.3. For further information on the latest version, see Maven Repository: Jakarta XML Binding API.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat