Add :classpath-jars and :project-files features #78
Conversation
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
When building for FIPS, we need to include the Bouncycastle FIPS jars in the package, but the code can not be included in the uberjar since they are signed jars. Therefore, we need to be able to pull down the version we are building against and then put them in the package. To do this, we pull the particular jars we are building against directly from the classpath and maven cache, and ezbake then puts them in the rpm/deb with the install command. For openvox-server, we need the non-FIPS jars in the staging dir as well since we do some gem installs during the packaging process and jruby-openssl is not compatible with Bouncycastle FIPS jars. So by omitting the :install key, it will copy them to staging, but not include them in the final package. We also need to be able to install a java.security.fips file. This adds a :project-files key that lets you point to any file and have that installed by the rpm/deb at the given path.
This was referenced Jan 22, 2026
bastelfreak
approved these changes
Jan 22, 2026
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.
When building for FIPS, we need to include the Bouncycastle FIPS jars in the package, but the code can not be included in the uberjar since they are signed jars. Therefore, we need to be able to pull down the version we are building against and then put them in the package.
To do this, we pull the particular jars we are building against directly from the classpath and maven cache, and ezbake then puts them in the rpm/deb with the install command.
For openvox-server, we need the non-FIPS jars in the staging dir as well since we do some gem installs during the packaging process and jruby-openssl is not compatible with Bouncycastle FIPS jars. So by omitting the :install key, it will copy them to staging, but not include them in the final package.
We also need to be able to install a java.security.fips file. This adds a :project-files key that lets you point to any file and have that installed by the rpm/deb at the given path.