prashantwason opened a new pull request, #20212:
URL: https://github.com/apache/hudi/pull/20212
### Describe the issue this Pull Request addresses
Every GitHub Actions CI job currently fails before compiling
(`validate-source` shows it as a RAT check failure) with:
```
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique:
com.fasterxml.jackson.module:jackson-module-afterburner:jar -> version
${fasterxml.version} vs ${fasterxml.jackson.databind.version}
```
GitHub's `ubuntu-24.04` runner image
[20261004](https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20261004.327)
upgraded Maven from 3.9.16 to 3.10.0. Maven 3.10 treats duplicate dependency
and dependencyManagement declarations as project-building errors instead of
warnings. The duplicates have been in the POMs since 2023.
### Summary and Changelog
Removes the duplicate declarations Maven 3.10 rejects, keeping what Maven
3.9 resolves today:
- `pom.xml`: `jackson-module-afterburner` was managed twice.
`${fasterxml.version}` and `${fasterxml.jackson.databind.version}` resolve to
the same version in every Spark profile, so the copy using
`${fasterxml.version}` is kept, matching `jackson-core` / `jackson-datatype-*`.
- `hudi-common/pom.xml`: `jackson-module-afterburner` declared twice,
identically.
- `hudi-aws/pom.xml`: `software.amazon.awssdk:sts` declared twice,
identically.
- `hudi-utilities/pom.xml`: `httpcore` declared once with
`${aws.sdk.httpcore.version}` (4.4.13) and again without a version. Maven 3.9
kept the first position with the later, managed version (4.4.16), so the first
declaration now takes the managed version and the second copy is dropped.
The CI error only showed the root POM because Maven stops there; the three
submodule duplicates fail next under 3.10.
### Impact
None at runtime. Effective POMs from Maven 3.9.16 are unchanged for
`hudi-common`, `hudi-aws` and `hudi-utilities` under `-Dspark3.5` and
`-Dspark4.2`. In the root POM the only difference is the removed duplicate
entry, which had the same resolved version.
### Risk Level
low. Verified locally:
- Maven 3.10.0 on current master reproduces the CI failure. With this
change, `mvn validate` reads every module's POM with no duplicate-declaration
errors under `-Dspark3.5` and `-Dspark4.2`.
- `help:effective-pom` from Maven 3.9.16, before vs. after, is identical
apart from the removed duplicate.
### Documentation Update
none
### Contributor's checklist
- [x] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [x] Enough context is provided in the sections above
- [ ] Adequate tests were added if applicable
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
