AmarGhugare opened a new pull request, #1863: URL: https://github.com/apache/commons-lang/pull/1863
Addresses [LANG-1425](https://issues.apache.org/jira/browse/LANG-1425). `DateUtils.parseDateStrictly` rejects the reported `.2860000` input because `S` parses an integer millisecond field, not a fraction of a second. Repeating `S` does not increase precision: `.0000286` is 286 milliseconds, while `.1` is one millisecond. Lenient parsing can normalize an out-of-range value into a different time. Document these distinctions in `DateUtils` and point callers needing fractional-second precision to `DateTimeFormatter`. Add seven parameterized test cases covering all four parsing overloads, one/three/seven `S` letters, leading zeros, valid boundaries and strict versus lenient handling of 1,000 and 2,860,000 milliseconds. Add the release-note entry. This is a documentation and tests change. Runtime parsing behavior is preserved; the tests establish the existing contract rather than requiring a runtime fix. Validation: - All 149 `DateUtilsTest` cases pass. - Default Maven build passes: 108,489 tests, zero failures/errors, 18 skipped, plus coverage, RAT, Checkstyle, compatibility, SpotBugs, PMD and Javadoc checks. - After refining the Javadoc wording, regenerated the Javadoc and reran Checkstyle successfully. - `git diff --check` passes. Checklist: - [x] Read the contribution guidelines. - [x] Read the ASF Generative Tooling Guidance. - [x] AI assistance disclosed: OpenAI Codex investigated the issue, wrote the documentation and tests, and ran the checks, following the contributor's request. The commit uses the required `Assisted-By:` trailer. - [x] Successful default Maven build. - [x] Added tests for the documented behavior. There is no runtime behavior change to test against a pre-fix implementation. - [x] Explained the problem, scope and validation. - [x] Commit subject references the Jira issue and describes the change. -- 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]
