[
https://issues.apache.org/jira/browse/FINERACT-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066705#comment-18066705
]
Hemanth Madhav commented on FINERACT-1298:
------------------------------------------
Hi! I've been following the discussion here regarding the migration from
{{java.util.Date}} to {{{}java.time{}}}. As part of my focus on 'Architectural
Hardening,' I'd like to help tackle this.
Since there are over 270 instances, I plan to start with a small, focused PR
targeting a single module (likely {{fineract-core}} or {{{}infrastructure{}}})
to ensure the transition to {{ZonedDateTime}} or {{LocalDate}} handles time
zones correctly as Michael suggested. I'll share my findings here before
opening the PR. Is there a specific module the maintainers would prioritize for
this migration?
> Replace java.util.Date API usages with java.time
> ------------------------------------------------
>
> Key: FINERACT-1298
> URL: https://issues.apache.org/jira/browse/FINERACT-1298
> Project: Apache Fineract
> Issue Type: Improvement
> Components: System
> Reporter: Michael Vorburger
> Priority: Major
> Labels: tech-debt
>
> https://github.com/apache/fineract/pull/1574 led us to run into
> https://errorprone.info/bugpattern/JavaUtilDate.
> I'll see if we can FINERACT-1297 by inhibiting that check, for now - but
> replacing all of our currently 276 {{java.util.Date}} usages with
> {{java.time}} does seem a good idea, that I'm personally in support of. (The
> 276 are what a quick "grep" filtered by anything in ".java" shows.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
