druid/35.0.0 package update

[octo-sts[bot]]

[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

Root Cause Analysis 🔍

The Maven build system cannot locate the org.eclipse.jetty.ee8:jetty-ee8-servlet:jar:9.4.56.v20240826 artifact in any of the configured repositories (maven.org, sigar, cflt-public). This appears to be caused by the pombump step that modified the jetty.version property from 12.0.25 to 9.4.56.v20240826, but the jetty-ee8-servlet artifact with version 9.4.56.v20240826 does not exist in the Maven 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) Original:

# Assuming the patches section exists or needs to be created

Replacement:

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

Content:

Add a new patch entry for jetty-ee8-servlet

Click to expand fix analysis

Analysis

All three similar fixes follow the same pattern: they resolve missing Maven artifacts by adding specific version corrections to pombump-deps.yaml files. The pattern shows that when Maven cannot find a specific version of a Jetty artifact, the solution is to specify the correct full version string (including the timestamp suffix like .v20240208 or .v20240826) in the pombump configuration. Each fix adds a new patch entry with groupId, artifactId, and the corrected version that exists in Maven Central.

Click to expand fix explanation

Explanation

The current build failure occurs because Maven cannot find the artifact org.eclipse.jetty.ee8:jetty-ee8-servlet:jar:9.4.56.v20240826. Based on the similar fixes, this is typically caused by the pombump step modifying versions but not accounting for the full version string that exists in Maven Central. The solution is to add a specific patch in the pombump-deps.yaml file that explicitly sets the correct version for this artifact. The version 9.4.56.v20240826 appears to be the correct one based on the error message, and this matches the pattern seen in Fix Example #2 where jetty-server version 9.4.56.v20240826 was successfully specified. The pombump-deps.yaml file allows overriding specific dependency versions during the Maven build process, which will ensure Maven can locate the correct artifact in the repository.

Click to expand alternative approaches

Alternative Approaches

• Create the pombump-deps.yaml file if it doesn't exist and add the jetty-ee8-servlet patch entry
• Check if there's a different correct version of jetty-ee8-servlet that should be used instead of 9.4.56.v20240826
• Verify if the jetty.version property should be reverted to a different version that has compatible ee8 artifacts

---

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

[aborrero]

I can't reproduce the test failure in my laptop :-(