FrankChen021 commented on PR #20021: URL: https://github.com/apache/druid/pull/20021#issuecomment-5295633480
Codex triage for PR #20021 at exact head `704a780df5b2eb02a0ee811a24663535c638985f`: - The exact diff against current master `b89f5d7e9acc89729a0f3c6c8647141f37c67c3a` changes only `maven-resolver-connector-basic` from `1.3.1` to `2.0.21` in `server/pom.xml` and `services/pom.xml`. - All five failed checks (`validate-dist`, `strict-compilation`, `static-checks-maven`, `packaging-check-jdk25`, and `openrewrite`) terminate on the same Maven Enforcer `RequireUpperBoundDeps` failure: Resolver 2.0.21 connector dependencies bring API/SPI/util 2.0.21 while Druid keeps transport, impl, SPI, API, util, and Maven Resolver Provider 3.6.0 on the 1.3.1 family. - Druid code in `PullDependencies` directly constructs the Resolver 1.x session/service stack and uses the scope/classpath-filter path; the [Resolver 2.x upgrade guide](https://maven.apache.org/resolver-archives/resolver-2.0.8/upgrading-resolver.html) requires coordinated session and filtering migration. The [Maven 3.6.0 dependency graph](https://maven.apache.org/ref/3.6.0/apache-maven/dependencies.html) also shows its provider coupled to Resolver 1.3.1. - A safe fix requires coordinated dependency, provider/runtime, source/test, and license-metadata changes; this is not a surgical version bump. No source change, rerun, rebase, or push was made. Closing as `CLOSED_HIGH_EFFORT/WONT_FIX_LARGE_CHANGE`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
