ekas-7 opened a new pull request, #878:
URL: https://github.com/apache/wayang/pull/878

   ## Summary
   - Upgrade the dependencies called out in #862: Log4j BOM 2.20.0 to 2.26.1 
(covers CVE-2025-68161), Jackson BOM 2.15.4 to 2.18.12, Netty 4.1.89.Final to 
4.1.140.Final, SnakeYAML 2.0 to 2.7, and Hadoop 3.3.6 to 3.4.3.
   - Drop the unused Log4j 1.2.17 dependency from `wayang-ml4all`. Nothing in 
that module imports it. Point its Hadoop client at `${hadoop.version}` instead 
of 3.0.3, and use the same property for the other hardcoded Hadoop pins 
(including the `wayang-basic` 3.4.0 override).
   - Remove unused root properties (`jaxb.version`, `commons-io.version`, 
`jodatime.version`, `jsonpath.version`, `mockk.version`) and the same unused 
copies in `wayang-applications`, so Jackson 2.15.4 cannot shadow the parent 
BOM. Align the `scala-12` profile Spark pin with the default 3.5.8.
   - Jackson stays on the 2.18 line already used in this repo. 
`wayang-api-utils` keeps its explicit `jackson-databind` 2.22.3 pin, which is 
newer than the BOM.
   
   JUEL is unchanged. The issue marks that migration as low priority, and it is 
only used to evaluate cost-model formulas. A full transitive scan 
(`dependency-check` or Dependabot in CI) is still worth adding separately, 
since Spark, Flink, and Hadoop will keep pulling older transitive libraries.
   
   Fixes #862
   
   ## Test plan
   - [x] Compile the modules that pick up these versions (core, basic, Spark, 
Giraph, API modules, spatial, benchmark, ml4all, applications) on JDK 17
   - [x] `wayang-core` tests, including `DynamicPluginTest` (SnakeYAML load 
path), plus the Java, Spark, and Scala-Java tests pulled in by `wayang-ml4all`
   - [ ] CI on this PR
   
   
   Made with [Cursor](https://cursor.com)


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

Reply via email to