fips-tests: add explicit jetty-alpn-java-client version after common dropped jetty-bom (7.8.x)#704
Merged
Hritwik Singhai (devhritwik) merged 1 commit intoMay 20, 2026
Conversation
…fips duplicate
The cp_packaging "Build rest-utils jar" job on 7.8.x is failing with:
'dependencies.dependency.version' for org.eclipse.jetty:jetty-alpn-java-client:jar
is missing. @ fips-tests/pom.xml line 50, column 21
Root cause: confluentinc/common PR #990 (9c2d2eaa22, merged into common/7.8.x via
8bc8dba5f1 on 2026-05-14) replaced jetty-bom with explicit per-artifact entries in
dependencyManagement, but only added the *-server variants
(jetty-alpn-conscrypt-server, jetty-alpn-java-server, jetty-alpn-server). The
jetty-alpn-java-client artifact, previously transitively managed by jetty-bom,
no longer has a version. Only common/7.8.x carries this regression; other branches
still use jetty-bom and are unaffected.
The proper fix is to add jetty-alpn-java-client to common's dependencyManagement,
but to unblock the 7.8.x package build immediately, declare the version explicitly
here using the inherited ${jetty.version} property.
Also drop the leftover hardcoded bcpkix-fips 1.0.7 dependency, which has been a
duplicate of the property-driven entry since the 7.7.x->7.8.x merge in Sep 2024
(f450bc4). Maven was emitting it as a warning today and would eventually become
an error.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Merged
4 tasks
Truc Nguyen (trnguyencflt)
approved these changes
May 20, 2026
This was referenced May 20, 2026
Hritwik Singhai (devhritwik)
deleted the
hsinghai/fix-rest-utils-7.8.x-jetty-alpn-java-client
branch
Hritwik Singhai (devhritwik)
added a commit
that referenced
this pull request
May 20, 2026
…fips duplicate (#705) The cp_packaging "Build rest-utils jar" job on 7.9.x is failing with: 'dependencies.dependency.version' for org.eclipse.jetty:jetty-alpn-java-client:jar is missing. @ fips-tests/pom.xml line 50, column 21 Root cause: confluentinc/common PR #990 (9c2d2eaa22) replaced jetty-bom with explicit per-artifact entries in dependencyManagement but only added the *-server variants. The regression landed on common/7.8.x via 8bc8dba5f1 on 2026-05-14 and then propagated to common/7.9.x via the recent 7.8.x->7.9.x merge (a9c100ddbc). jetty-alpn-java-client, previously transitively managed by jetty-bom, no longer has a version. The proper fix is to add jetty-alpn-java-client to common's dependencyManagement, but to unblock the 7.9.x package build immediately, declare the version explicitly here using the inherited ${jetty.version} property. Mirrors PR #704 on 7.8.x. Also drop the leftover hardcoded bcpkix-fips 1.0.7 dependency, which has been a duplicate of the property-driven entry since the 7.7.x->7.8.x merge in Sep 2024 and propagated down through 7.9.x. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
7.8.xis failing because Maven can no longer resolve a version fororg.eclipse.jetty:jetty-alpn-java-client(failing job: https://semaphore.ci.confluent.io/jobs/87a001a4-c757-4d91-b379-4a0f9de9c9d2).confluentinc/commonPR #990 (9c2d2eaa22, merged intocommon/7.8.xvia8bc8dba5f1on 2026-05-14), which replacedjetty-bomwith explicit per-artifact entries independencyManagementbut only added the*-servervariants.jetty-alpn-java-client, previously transitively managed byjetty-bom, was missed. Onlycommon/7.8.xcarries this regression; other release branches still usejetty-bomand are unaffected — that is why this failure is isolated torest-utils/7.8.x.jetty-alpn-java-clienttocommon'sdependencyManagement. To unblock the package build immediately, this PR declares the version explicitly infips-tests/pom.xmlusing the inherited${jetty.version}property.bcpkix-fips 1.0.7dependency that has been emitting a Maven warning since the 7.7.x→7.8.x merge in Sep 2024 (f450bc4e42).Test plan
mvn -B -Pcp-build -DskipTestssucceeds forrest-utils-fips-tests'dependencies.dependency.version' for org.eclipse.jetty:jetty-alpn-java-client:jar is missingerrorbcpkix-fipsduplicate warning is gone🤖 Generated with Claude Code