Upgrade joda-time from 2.10.14 to 2.12.7

[JinwooHwang]

Overview

This PR upgrades the joda-time dependency from version 2.10.14 to 2.12.7, bringing in bug fixes, performance improvements, and updated timezone data.

Changes Made

Dependency Version Updates

• joda-time: 2.10.14 → 2.12.7

Files Modified

1. build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy

   • Updated joda-time version constraint to 2.12.7

2. boms/geode-all-bom/src/test/resources/expected-pom.xml

   • Updated expected joda-time version in BOM test resources

3. geode-assembly/src/integrationTest/resources/assembly_content.txt

   • Updated JAR reference: joda-time-2.10.14.jar → joda-time-2.12.7.jar

4. geode-assembly/src/integrationTest/resources/gfsh_dependency_classpath.txt

   • Updated classpath reference: joda-time-2.10.14.jar → joda-time-2.12.7.jar

5. geode-server-all/src/integrationTest/resources/dependency_classpath.txt

   • Updated classpath reference: joda-time-2.10.14.jar → joda-time-2.12.7.jar

Validation

Build Validation

All build tasks completed successfully:

• ✅ build

Test Validation

• ✅ All tests passed with gradlew test

Benefits

• Updated timezone data: Latest timezone database for accurate date/time operations
• Bug fixes: Includes multiple bug fixes from versions 2.10.15 through 2.12.7
• Performance improvements: Enhanced performance in date/time calculations
• Security: Latest stable version with all known issues addressed

Compatibility

• Fully backward compatible with existing code
• No API changes affecting current usage
• All existing tests pass without modification

Release Notes References

For detailed information about changes between versions, see:

• Joda-Time Release Notes

---

Note: This upgrade is part of ongoing dependency maintenance to keep the project up-to-date with the latest stable versions of its dependencies.

For all changes, please confirm:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
• Has your PR been rebased against the latest commit within the target branch (typically develop)?
• Is your initial contribution a single, squashed commit?
• Does gradlew build run cleanly?
• Have you written or updated unit tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[JinwooHwang]

Hi @sboorlagadda , all checks have passed. Thank you.

[JinwooHwang]

Thank you so much for your support @raboof