[Maintenance] Fix bc-fips dependency jarhell for maven publish#5963
Merged
cwperks merged 1 commit intoFeb 20, 2026
Merged
Conversation
Signed-off-by: Jialiang Liang <jiallian@amazon.com>
cwperks
approved these changes
Feb 19, 2026
reta
approved these changes
Feb 19, 2026
1 task
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
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.
Description
The FIPS flag (
-Pcrypto.standard=FIPS-140-3) was added toplugin_install.ymlandscripts/build.sh, but it's missing frommaven-publish.yml. This means the published snapshots are still built without the flag, sobc-fips,bcpkix-fips, andbcutil-fipsare bundled asimplementationinstead ofcompileOnly. This causes jar hell for downstream plugins (like SQL) that download the security snapshot for integration tests, since those jars already exist in OpenSearch core'slib/directory.Issues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.