Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-2591

[Docs]: Red Hat does not provide a productized Java 11/Mandrel 22.3 image with RHBQ 2.13

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.13-Fireball.GA
    • 2.13-Fireball.GA
    • team/docs
    • None

      https://pantheon.corp.redhat.com/pantheon/preview/latest/1c09f0fb-adbf-4342-bd50-41d07fcc38a8?rerender=true#redhat_does_not_offer_a_java_11_based_image_for_mandrel_22_3

      Content updates imported into PV II.

      Ready for QE verification.

      Setting Jira to Testing.

       

      ENG SME contact: cescoffi@redhat.com

      Context: We must make it clear in the RN for 2.13 that Red Hat does not provide a productized and supported Java 11/Mandrel 22.3 base image for building native executables with RHBQ.
      Due to resource and process-efficiency limitations, RH can only ship and support a Java 17-based Mandrel 22.3 native executable base image.
      A Java 11-based version of this image is available in community only. This image is not supported in production, although it can be used for development purposes outside of production environments.

      Customer impact:
      Even though the supported Java 17 image is backwards compatible with Java 11 application enough to not disrupt production native executable builds for RHBQ customers, there are certain corner cases in which a straightforward upgrade might cause build failures on production apps, requiring an update to the build configuration to remedy the issue on the customer's side.
      One such case is when the native executable build is part of an incremental (or multi-stage) build process.
      For more details, please reach out to Clement.

       

              rdlugyhe Rolfe Dlugy-Hegwer
              ssitani Stefan Sitani (Inactive)
              Antonio Fernandez Alhambra Antonio Fernandez Alhambra (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: