Remove FIPS BC jars from ezbake-fips dependencies#274
Merged
bastelfreak merged 1 commit intomainfrom Apr 25, 2026
Merged
Conversation
The FIPS BouncyCastle jars (bc-fips, bcpkix-fips, bctls-fips) cannot be in :ezbake-fips :dependencies alongside bcpkix-jdk18on because bc-fips has Sealed: true in its manifest and shares packages with bcprov-jdk18on (a transitive dependency of bcpkix-jdk18on), causing a JVM sealing violation at startup. The FIPS jars remain in :managed-dependencies for version pinning and in :classpath-jars so ezbake copies them to staging. With the ezbake fallback for resolving classpath-jar artifacts from managed-dependencies, they no longer need to be in :dependencies. Signed-off-by: nmburgan <13688219+nmburgan@users.noreply.github.com>
|
The rpm/deb packages and the JAR file for openvox-server are available in a zip archive: |
bastelfreak
approved these changes
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The FIPS BouncyCastle jars (bc-fips, bcpkix-fips, bctls-fips) cannot be in :ezbake-fips :dependencies alongside bcpkix-jdk18on because bc-fips has Sealed: true in its manifest and shares packages with bcprov-jdk18on (a transitive dependency of bcpkix-jdk18on), causing a JVM sealing violation at startup.
The FIPS jars remain in :managed-dependencies for version pinning and in :classpath-jars so ezbake copies them to staging. With the ezbake fallback for resolving classpath-jar artifacts from managed-dependencies, they no longer need to be in :dependencies.
Requires OpenVoxProject/ezbake#94