upgrade all according to versions:display-plugin-updates

also requireMavenVersion to a recent-ish maven version (3.8.1), from about the same
period as the java 17 release. Hopefully this reduces potential problems.

except
maven-site-plugin .............................. 3.9.1 -> 4.0.0-M8
    -> 3.12.1 latest release not milestone
org.springframework.boot:spring-boot-maven-plugin .. 2.6.6 -> 3.1.0
    -> wait for runtime springboot 3 migration

pom.xml

@@ -93,23 +93,23 @@
     <properties>
         <maven.core.version>3.8.1</maven.core.version>
 
-        <maven.antrun.version>3.0.0</maven.antrun.version>
-        <maven.assembly.version>3.3.0</maven.assembly.version>
+        <maven.antrun.version>3.1.0</maven.antrun.version>
+        <maven.assembly.version>3.6.0</maven.assembly.version>
         <maven.buildhelper.version>3.4.0</maven.buildhelper.version>
         <maven.clean.version>3.2.0</maven.clean.version>
         <maven.compiler.version>3.11.0</maven.compiler.version>
-        <maven.dependency.version>3.1.2</maven.dependency.version>
-        <maven.deploy.version>2.8.2</maven.deploy.version>
-        <maven.enforcer.version>3.2.1</maven.enforcer.version>
-        <maven.gpg.version>1.6</maven.gpg.version>
-        <maven.install.version>3.1.0</maven.install.version>
+        <maven.dependency.version>3.6.0</maven.dependency.version>
+        <maven.deploy.version>3.1.1</maven.deploy.version>
+        <maven.enforcer.version>3.3.0</maven.enforcer.version>
+        <maven.gpg.version>3.1.0</maven.gpg.version>
+        <maven.install.version>3.1.1</maven.install.version>
         <maven.jar.version>3.3.0</maven.jar.version>
-        <maven.projectinforeports.version>3.1.1</maven.projectinforeports.version>
-        <maven.release.version>2.5.3</maven.release.version>
+        <maven.projectinforeports.version>3.4.5</maven.projectinforeports.version>
+        <maven.release.version>3.0.1</maven.release.version>
         <maven.resources.version>3.3.1</maven.resources.version>
-        <maven.site.version>3.9.1</maven.site.version>
-        <maven.surefire.version>3.1.0</maven.surefire.version>
-        <maven.versions.version>2.8.1</maven.versions.version>
+        <maven.site.version>3.12.1</maven.site.version>
+        <maven.surefire.version>3.1.2</maven.surefire.version>
+        <maven.versions.version>2.16.0</maven.versions.version>
 
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     </properties>

powsybl-parent/pom.xml

@@ -31,10 +31,10 @@
         <!-- javac's source and target arguments accept both 1.8 and 8, but release accepts only 8 -->
         <java.version>8</java.version>
 
-        <maven.buildnumber.version>3.1.0</maven.buildnumber.version>
-        <maven.checkstyle.version>3.2.2</maven.checkstyle.version>
-        <maven.failsafe.version>3.1.0</maven.failsafe.version>
-        <maven.gmavenplus.version>1.11.1</maven.gmavenplus.version>
+        <maven.buildnumber.version>3.2.0</maven.buildnumber.version>
+        <maven.checkstyle.version>3.3.0</maven.checkstyle.version>
+        <maven.failsafe.version>3.1.2</maven.failsafe.version>
+        <maven.gmavenplus.version>3.0.0</maven.gmavenplus.version>
         <!--
             For groovydoc, we must use the same version as the project's groovy version. Standardize on the groovy.version property.
             For projects which don't use groovy at all, this means the pluginmanagement will hold an invalid <version> definition
@@ -44,11 +44,11 @@
             so projects can detect errors early and fix their groovydoc configuration.
         -->
         <maven.groovydoc.version>${groovy.version}</maven.groovydoc.version>
-        <maven.jacoco.version>0.8.8</maven.jacoco.version>
-        <maven.javadoc.version>3.2.0</maven.javadoc.version>
+        <maven.jacoco.version>0.8.10</maven.jacoco.version>
+        <maven.javadoc.version>3.5.0</maven.javadoc.version>
         <maven.plugin.version>3.9.0</maven.plugin.version>
-        <maven.shade.version>3.2.4</maven.shade.version>
-        <maven.source.version>3.2.1</maven.source.version>
+        <maven.shade.version>3.4.1</maven.shade.version>
+        <maven.source.version>3.3.0</maven.source.version>
         <!--
             issue opened to fix the warnings from maven 3.9.2 ('Plugin should declare these Maven artifacts in `provided` scope') :
             https://github.com/mojohaus/templating-maven-plugin/issues/54

powsybl-parent/powsybl-parent-ws/pom.xml

@@ -27,7 +27,7 @@
         <!-- todo: Upgrade maven jib version to fix warning about provided scope when this is released https://github.com/GoogleContainerTools/jib/pull/4034 -->
         <maven.jib.version>3.3.2</maven.jib.version>
         <maven.spring-boot.version>2.6.6</maven.spring-boot.version>
-        <maven.git-commit-id.version>5.0.1</maven.git-commit-id.version>
+        <maven.git-commit-id.version>6.0.0</maven.git-commit-id.version>
 
         <jib.from.image>powsybl/java:2.0.0</jib.from.image>