Add rpminspect.yaml to turn off Java bytecode inspections
java-17-openjdk deliberately produces Java 17 bytecode, not the default Java 11 bytecode
Resolves: rhbz#2109106

Revert the following changes until copy-java-configs has adapted to relative symlinks:
The move of turning on system security properties is retained so we don't ship with them off
Related: rhbz#2084650

Returned absolute symlinks
Relative symlinks are breaking cjc, and deeper investigations are necessary
- why cjc intentionally skips relative symllinks
Images have to be workarounded differently
Related: rhbz#2084650

Update to jdk-17.0.4.0+8
Update release notes to 17.0.4.0+8
Need to include the '.S' suffix in debuginfo checks after JDK-8284661
Print release file during build, which should now include a correct SOURCE value from .src-rev
Update tarball script with IcedTea GitHub URL and .src-rev generation
Include script to generate bug list for release notes
Update tzdata requirement to 2022a to match JDK-8283350
Move EA designator check to prep so failures can be caught earlier
Make EA designator check non-fatal while upstream is not maintaining it
Explicitly require crypto-policies during build and runtime for system security properties
Make use of the vendor version string to store our version & release rather than an upstream release date
Include a test in the RPM to check the build has the correct vendor information.
Rebase FIPS patches from fips-17u branch and simplify by using a single patch from that repository
Rebase RH1648249 nss.cfg patch so it applies after the FIPS patch
Enable system security properties in the RPM (now disabled by default in the FIPS repo)
Improve security properties test to check both enabled and disabled behaviour
Run security properties test with property debugging on
Turn on system security properties as part of the build's install section
Move cacerts replacement to install section and retain original of this and tzdb.dat
Run tests on the installed image, rather than the build image
Introduce variables to refer to the static library installation directories
Use relative symlinks so they work within the image
Run debug symbols check during build stage, before the install strips them
Resolves: rhbz#2084650
Resolves: rhbz#2099913
Resolves: rhbz#2108206
Resolves: rhbz#2108209
Resolves: rhbz#2106521

Fix issue where CheckVendor.java test erroneously passes when it should fail.
Add proper quoting so '&' is not treated as a special character by the shell.
Related: rhbz#2084650

RH2007331: SecretKey generate/import operations don't add the CKA_SIGN attribute in FIPS mode
Resolves: rhbz#2108190

April 2022 security update to jdk 17.0.3+7
Update to jdk-17.0.3.0+7 tarball
Update release notes to 17.0.3.0+7
Add missing README.md and generate_source_tarball.sh
Resolves: rhbz#2073576

Enable AlgorithmParameters and AlgorithmParameterGenerator services in FIPS mode
Resolves: rhbz#2052070

Introduce tests/tests.yml, based on the one in java-11-openjdk
Resolves: rhbz#2058493

Use 'sql:' prefix in nss.fips.cfg as F35+ no longer ship the legacy
Resolves: rhbz#2023536

Detect NSS at runtime for FIPS detection
Turn off build-time NSS linking and go back to an explicit Requires on NSS
Resolves: rhbz#2051605

Add JDK-8275535 patch to fix LDAP authentication issue.
Resolves: rhbz#2053256

Storing and restoring alterntives during update manually
Fixing Bug 2001567 - update of JDK/JRE is removing its manually selected alterantives and select (as auto) system JDK/JRE
- The move of alternatives creation to posttrans to fix:
- Bug 1200302 - dnf reinstall breaks alternatives
- Had caused the alternatives to be removed, and then created again,
- instead of being added, and then removing the old, and thus persisting
- the selection in family
- Thus this fix, is storing the family of manually selected master, and if
- stored, then it is restoring the family of the master
Resolves: rhbz#2008200

Family extracted to globals
Resolves: rhbz#2008200

alternatives creation moved to posttrans
Thus fixing the old reisntall issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1200302
https://bugzilla.redhat.com/show_bug.cgi?id=1976053
Resolves: rhbz#2008200

Separate crypto policy initialisation from FIPS initialisation, now they are no longer interdependent
Resolves: rhbz#2051590