druid/35.0.0 package update

[octo-sts[bot]]

Commit: f6712c6694a2b95961607c3ceac0123418641d40

[octo-sts[bot]]

📦 Build Failed: Missing Dependency

Could not find artifact org.eclipse.jetty.ee8:jetty-ee8-servlet:jar:9.4.56.v20240826 in maven.org (https://repo.maven.apache.org/maven2/)

Build Details

Category	Details
Build System	Maven
Failure Point	Failed to execute goal on project druid-processing: Could not resolve dependencies for project org.apache.druid:druid-processing:jar:35.0.0

Root Cause Analysis 🔍

The Maven build failed because it cannot find the dependency org.eclipse.jetty.ee8:jetty-ee8-servlet:jar:9.4.56.v20240826 in any of the configured repositories (maven.org, sigar, cflt-public). This appears to be related to a version mismatch where the pombump tool patched the jetty.version property from 12.0.25 to 9.4.56.v20240826, but the jetty-ee8-servlet artifact doesn't exist for that version in the available repositories.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• https://github.com/wolfi-dev/os/pull/46986

Suggested Changes

File: druid/pombump-deps.yaml

• addition (patches section) Replacement:

  - groupId: org.eclipse.jetty.ee8
    artifactId: jetty-ee8-servlet
    version: 9.4.56.v20240826

Content:

Add a new patch entry for the missing jetty-ee8-servlet dependency

Click to expand fix analysis

Analysis

All three similar fixes follow the same pattern: they address missing Jetty artifacts by adding specific version patches to pombump-deps.yaml files. The fixes consistently use the full Jetty version format with timestamp suffixes (e.g., 9.4.54.v20240208, 9.4.56.v20240826) rather than incomplete versions. The pattern shows that when pombump automatically patches Jetty versions, it sometimes generates incorrect or non-existent version numbers that need to be corrected with explicit patches in the pombump-deps.yaml configuration.

Click to expand fix explanation

Explanation

The current build failure is caused by pombump automatically patching the jetty.version to 9.4.56.v20240826, but the jetty-ee8-servlet artifact doesn't exist for that specific version in Maven Central. Based on the pattern from similar fixes, we need to create a pombump-deps.yaml file (or add to existing one) that explicitly specifies the correct version for the jetty-ee8-servlet artifact. The version 9.4.56.v20240826 appears to be the intended version based on the error message and the pattern from Fix Example #2 which successfully used this exact version for jetty-server. This approach allows us to override pombump's automatic version detection with a manually verified version that exists in the Maven repository.

Click to expand alternative approaches

Alternative Approaches

• Verify if jetty-ee8-servlet:9.4.56.v20240826 actually exists in Maven Central and if not, use the latest available 9.4.x version like 9.4.54.v20240208
• Check if there's a newer Jetty version (like 11.x or 12.x series) that includes the ee8 servlet module and update the entire Jetty dependency chain
• Investigate if the ee8 servlet dependency can be replaced with a different Jetty servlet module that's available in the target version

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

[aborrero]

working on https://github.com/wolfi-dev/os/pull/71178 which has more context