Update to Java 17

[So-Fras]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines

Does this PR already have an issue describing the problem?
No

What kind of change does this PR introduce?
Update to Java 17
A test had to be modified in order to pass when run with Java 17 (French thousand separator was changed from Non-breakable space - NBSP - to Narrow non-breakable space - NNBSP - in Java 13 due to CLDR 35.1 support).

Does this PR introduce a breaking change or deprecate an API?
Yes

• The Breaking Change or Deprecated label has been added
• The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

[So-Fras]

Now I think about it, is there a reason to have a conditional test for the Java version? Once we switch to Java 17, will users be able to run tests with older Java versions anyway?

[olperr1]

Now I think about it, is there a reason to have a conditional test for the Java version? Once we switch to Java 17, will users be able to run tests with older Java versions anyway?

You are right, the conditional test was only to prepare the Java 17 upgrade. Since this PR covers also the upgrade, the Java 11 alternative would never be reached.
Thus we could either:

• remove the java11 branch;
• split this PR in 2 (the test adaptation + the java17 upgrade), if we want to defer the upgrade in powsybl-diagram.

As we will soon merge the powsybl-core java 17 upgrade, it's maybe easier to choose the first alternative.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication