New timestamp format using BigDecimal and Instant

[adamsero]

No description provided.

[sbernard31]

@adamsero, looking at your PR, I see that github action does not work as expected.
When error is detected, comments should be added to PR to help you to resolve it. This should like this sbernard31#12.

I create #1314 to try to resolve it.

[adamsero]

@sbernard31 regarding your comment, specifically

Could you not fix the last one about Check Android API Compliance ?

I'm getting a bunch of errors caused by the use of Instant class, since it's not compatible with Android API v19 as defined in build-config/lib-build-config/pom.xml:

<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-19</artifactId>
    <version>4.4.2_r4</version>
</signature>

The fact that we check against API v19 released in 2013 means that we can't use any feature of Java 1.8 (from 2014), so we either have to bump the API version (I don't know what issues could arise from that) or this PR stays useless since I can't use the Instant class.

[sbernard31]

About Undefined reference: java.time.Instant :

Sorry I didn't think to check if this was available.
Strange you didn't face this issue sooner. I guess you don't often run maven locally ?

I continue the discussion at #1304

[sbernard31]

After discussion at #1304 (comment).

We decide to bump android API level from 19 to 26.
So from

<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-19</artifactId>
    <version>4.4.2_r4</version>
</signature>

to something like

<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-26</artifactId>
    <version>8.0.0_r2</version>
</signature>

[adamsero]

We should be good now @sbernard31, waiting for you to bump the API version if you don't have any more issues to fix.

[adamsero]

@sbernard31 I created some tests and added some exception throws in the util method. My question is, can we possibly be done with this PR and M9 by the end of the week? It would be really good timing if we could.

[sbernard31]

My question is, can we possibly be done with this PR and M9 by the end of the week? It would be really good timing if we could.

We can try.

[sbernard31]

I think we are good now ?

I let you deal with Maven / Code Check github action and upgrade the Android level API.

Then maybe you could rebase on `master and, squash all commits in one ? (then push force)

Eventually you can Android level API change in a separated commit, if you do that then this android level api change commit should be before the modification. (but again it's ok if you squash all in 1)

Last point, maybe you can refer #1304 issue in your commit header.

[adamsero]

Should be good to go. Good to finally see a green checkmark 🙂

[sbernard31]

Thx for the contribution 🙏 !