From Fedora Project Wiki

Build all JDKs in Fedora against in-tree libraries and with static stdc++lib


This is initial step to move JDKs to be more like other JDKs, to build proper transferable images, and to lower certification burden of each binary. Long storyshort, first step in:

This first step will move, one by one, individual JDKs in F37 to be built --with-stdc++lib=static and against in-tree (bundeld) libraries: --with-zlib="bundled" --with-freetype="bundled" --with-libjpeg="bundled" --with-giflib="bundled" --withlibpng="bundled" --with-lcms="bundled" --with-harfbuzz="bundled"

We already made a heavy testing of the behavior, and user should not face negative experience. Still I'm not sure if this testing can ever be enough, considering all the use-cases we do not know.

non goal

It is not goal to embed any security libraries. JDK is using several security providers, and all are currently loaded dynamically in runtime. Still there is remaining issue with cacerts:


Current status

  • System or Self contained change? By the changes done, this is Self Contianed Change. However from view of impact, and possible world notification, it is more System Wide Change.
  • Targeted release: Fedora Linux 38
  • Last updated: 2022-09-07
  • devel thread
  • FESCo issue: #2794
  • Tracker bug: #2097516
  • Release notes tracker: #848

Detailed Description

Please see for whole picture

Please see for this particular step. I would rather keep the details in the main page then here.

See very valuable thread about the topic:


According to short investigations, there are already precedents, where certification is a reason to build once, certificate, and repack.

According to developers, the non-portbale JDK is causing upredicted behavior different from other JDK vendors

According to JDK packagers and testers, there is to much JDKs now, and the is the only way out

Benefit to Fedora

Please see for whole picture.

This particualr proposal's main benefit will be that Fedora's JDKs as packed in RPMs will again start to resemble upstream JDKs and other vendors build, and some platfrom specific issues disappear, while JDKs remain same in view of system integration and user expereince


  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

The compatibility and upgrade path should remain completely smooth.

How To Test

Install system JDK (java-17-openjdk) and ru your favorite application or development. No regression should be noted.

User Experience

Because of in-tree libraries, minimal image or font rendering differences canbe spotted after very detailed investigations - - still, no of th e should be hit by this proposal.


No dependent packages should notice the change.

Contingency Plan


Release Notes