Issue 10068

[andrii0lomakin]

Fix of issue #10068 .

1. Exception on the Linux platform was fixed during storage initialization.
2. The build number is stored correctly during the build of the project.

[andrii0lomakin]

This branch was based on 4.0.x, so I had to rebase a bunch of commits.

[tglman]

I'm planning to delete completely this class on 4.0.x so no need to do evolution on this

[andrii0lomakin]

I got it: -) I planned to do the same.

[andrii0lomakin]

I have also added maven.release property to avoid usage of API introduced in later JDKs.

[tglman]

Hi,

A quick review on this:

this commit 7ee1aa6 should be already somehow on develop this: f92ddb4 we do support only java17+ so we cannot use jdk18+ dependencies develop should be already in a good state for cert generation

this: 0ba2b14 is quite welcome, but it has a bit of formatting in it that maybe should not be in this commit

this: 573b160 is good to merge
this: 53a3936 good to merge
this: 404b3fc more than happy to merge it
this: a280f2b good to merge as well

these two:d289fd3, d6d8909 should be redundant as well, it's ok if some of the good commit introduce some specific java 21 changes

Code formatting, so : 18fe41d and 60bcf31 I do not want yet to upgrade the development formatter for another 1/2 weeks, because of some old changes I've pending, so I would prefer keep these out.

[andrii0lomakin]

@tglman jdk8on is about 1.8+ not about 18+

[andrii0lomakin]

@tglman may I ask you to add comments on commit level, so we can discuss observation ?

[andrii0lomakin]

It is hard to discuss observations otherwise

[andrii0lomakin]

@tglman I will roll back code formatting.

[andrii0lomakin]

@tglman, if you have already added changes, can we go with the current code formatter? The old one does not support new language features. Also as I mentioned, jdk18on dependency is not about Java 18, it is about Java 1.8+