fix(build): exclude nested .mvn directories from the RAT check

[wombatu-kun]

Describe the issue this Pull Request addresses

Closes #19461.

The RAT check inside the source release fails on hudi-trino/.mvn/modernizer/violations.xml and violations-production-code-only.xml. Both are tracked without an ASF header, and the root pom's <exclude>.mvn/**</exclude> does not cover them because a RAT exclude is relative to the project basedir, so it only matches <root>/.mvn/**. In the workspace .gitignore hides them, but create_source_directory.sh strips .gitignore from the tarball.

Summary and Changelog

• Root pom.xml: widen the apache-rat exclude from .mvn/** to **/.mvn/**, and move it out from under the <!-- local files not in version control --> comment, which no longer describes it.

Verified on the tree the release job validates, built with create_source_directory.sh:

tree	before	after
source release directory	Unapproved: 2, BUILD FAILURE	Unapproved: 0, BUILD SUCCESS
workspace	Unapproved: 0	Unapproved: 0

A headerless file planted at <root>/.mvn/ is excluded by **/.mvn/** exactly as by .mvn/**, so no coverage is lost.

Impact

Unblocks validate_staged_release.sh for the next release cut. No production code, API, config, or format change.

Risk Level

low - build configuration only, and the change only widens an existing exclude.

Documentation Update

none

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable
• CI passes on my PR

[wombatu-kun]

@voonhous Hi! please review this tiny fix when you have a sec

[hudi-agent]

⚠️ 🤖 This review was generated by an AI agent and may contain mistakes. Please verify any suggestions before applying.

Thanks for working on this! The PR widens the apache-rat exclude from .mvn/** to **/.mvn/** so nested .mvn directories (e.g. hudi-trino/.mvn/) are covered in the source-release tarball where .gitignore is stripped. No issues flagged from this automated pass — a Hudi committer or PMC member can take it from here for a final review.

cc @yihua

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.81%. Comparing base (64afac0) to head (51b5a2a).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #19462      +/-   ##
============================================
- Coverage     76.81%   76.81%   -0.01%     
+ Complexity    33770    33767       -3     
============================================
  Files          2576     2576              
  Lines        143457   143457              
  Branches      17589    17589              
============================================
- Hits         110201   110193       -8     
- Misses        25010    25017       +7     
- Partials       8246     8247       +1     

Components	Coverage Δ
hudi-common	82.26% <ø> (ø)
hudi-client	81.82% <ø> (-0.03%)	⬇️
hudi-flink	83.97% <ø> (+<0.01%)	⬆️
hudi-spark-datasource	74.22% <ø> (ø)
hudi-utilities	73.63% <ø> (-0.04%)	⬇️
hudi-cli	15.32% <ø> (ø)
hudi-hadoop	63.49% <ø> (ø)
hudi-sync	70.92% <ø> (+0.05%)	⬆️
hudi-io	79.60% <ø> (ø)
hudi-timeline-service	83.74% <ø> (-0.49%)	⬇️
hudi-cloud	64.00% <ø> (ø)
hudi-kafka-connect	53.96% <ø> (+0.76%)	⬆️

Flag	Coverage Δ
common-and-other-modules	49.50% <ø> (+<0.01%)	⬆️
flink-integration-tests	48.80% <ø> (+<0.01%)	⬆️
hadoop-mr-java-client	43.41% <ø> (-0.01%)	⬇️
integration-tests	13.58% <ø> (-0.01%)	⬇️
spark-client-hadoop-common	48.68% <ø> (-0.01%)	⬇️
spark-java-tests	51.31% <ø> (-0.03%)	⬇️
spark-scala-tests	47.23% <ø> (+0.01%)	⬆️
utilities	36.56% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 13 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hudi-bot]

CI report:

• 51b5a2a Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build