zhengruifeng opened a new pull request, #59635: URL: https://github.com/apache/spark/pull/59635
### What changes were proposed in this pull request? Use Spark 4.2.0 as the previous artifact version for MiMa, and switch `GenerateMIMAIgnore`'s class finder from ASM8 to ASM9. Add four narrow MiMa exclusions for the private `ProxyRedirectHandler.MutableFieldsWrapper` and `ResponseWrapper` implementation members whose Jetty types are shaded in the published 4.2.0 artifact. ### Why are the changes needed? The 4.0.0 baseline does not comprehensively check released signatures introduced in Spark 4.1 and 4.2. Updating the baseline brings those APIs into the configured binary-compatibility checks. The 4.2.0 artifacts also contain sealed interfaces. ASM8 cannot visit their `PermittedSubclasses` attribute, so the exclusion scanner must request ASM9. The first run against 4.2.0 found only four Jetty shading differences in explicitly private nested wrapper classes. The added exclusions are limited to those private implementation details; existing compatibility exclusions are retained. Please also backport to `branch-4.x` and `branch-4.3`. ### Does this PR introduce _any_ user-facing change? No runtime API change. Build-time binary compatibility checks now compare against Spark 4.2.0. ### How was this patch tested? Ran the standard `dev/mima` pipeline with Java 17. After adding the four private Jetty-wrapper exclusions, the pipeline completed successfully, including generation of private API exclusions and binary-compatibility checks for all configured MiMa projects against 4.2.0. Also ran `git diff --check` and checked changed Scala lines for ASCII and the 100-column limit. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: OpenAI Codex (GPT-6) -- 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]
