FrankChen021 commented on PR #20019:
URL: https://github.com/apache/druid/pull/20019#issuecomment-5295702348

   CLOSED_HIGH_EFFORT/WONT_FIX_LARGE_CHANGE
   
   At exact PR head f03a11c588dfc26176242a7e2d4671701297a52d, the only PR diff 
against current master b89f5d7e9acc89729a0f3c6c8647141f37c67c3a is 
services/pom.xml: org.apache.maven.resolver:maven-resolver-util 1.3.1 -> 2.0.21.
   
   Effective Maven resolution leaves maven-resolver-api, spi, impl, 
connector-basic, and transport-http at 1.3.1, plus maven-resolver-provider 
3.6.0; util 2.0.21 requests api 2.0.21. static-checks, openrewrite, packaging, 
strict-compilation, and validate-dist fail RequireUpperBoundDeps on that split. 
JDK25 M*,P*,O* reports 12 PullDependenciesTest failures with 
NoClassDefFoundError: org/eclipse/aether/scope/SystemDependencyScope. 
web-checks has an unrelated Codecov upload TypeError, but its distribution 
phase also fails with the same PR-caused missing class.
   
   Resolver 2.x removes DefaultServiceLocator and changes session/scope APIs. 
Druid PullDependencies main/test directly use DefaultServiceLocator and 
MavenRepositorySystemUtils.newSession; the distribution package and documented 
pull-deps command execute this runtime path. A safe 2.x update therefore 
requires coordinated Resolver-family/provider alignment, source and test 
migration, distribution validation, and license metadata updates. Reverting to 
1.3.1 would make this PR a no-op, so there is no surgical fix.
   
   References: 
https://maven.apache.org/resolver-archives/resolver-2.0.8/upgrading-resolver.html
 and https://github.com/apache/maven-resolver/releases/tag/maven-resolver-2.0.21
   
   Closing as CLOSED_HIGH_EFFORT/WONT_FIX_LARGE_CHANGE. No rebase, push, rerun, 
approval, or merge.


-- 
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]

Reply via email to