Update invoker plugin to 3.9.1 to Support Java 25

[Bukama]

No description provided.

[Bukama]

@slawekjaranowski The It were failing due the same "unsupportet class file version 69" error. I'm now trying to also define the invoker plugin in the IT parent project.

[Bukama]

So what I see from log. The failing IT is the following, however it has invoker-plugin 3.9.1 and current compiler plugin (3.14.1) is defined

[INFO] Building: mini-jar-jdk11+/pom.xml
[INFO] run post-build script verify.bsh
[INFO] java.lang.IllegalStateException: wanted path is missing: junit/framework/TestCase.class
[INFO] mini-jar-jdk11+/pom.xml .......................... FAILED (2.475 s)

[...]

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper (file:/home/runner/.m2/wrapper/dists/apache-maven-3.6.3/5542c391/lib/guava-25.1-android.jar)
WARNING: Please consider reporting this to the maintainers of class com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release

[...]

Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 69
at org.vafer.jdeb.shaded.objectweb.asm.ClassReader. (ClassReader.java:200)
at org.vafer.jdeb.shaded.objectweb.asm.ClassReader. (ClassReader.java:180)
at org.vafer.jdeb.shaded.objectweb.asm.ClassReader. (ClassReader.java:166)
at org.vafer.jdeb.shaded.objectweb.asm.ClassReader. (ClassReader.java:288)
at org.vafer.jdependency.Clazzpath.addClazzpathUnit (Clazzpath.java:179)
at org.vafer.jdependency.Clazzpath.addClazzpathUnit (Clazzpath.java:151)
at org.apache.maven.plugins.shade.filter.MinijarFilter. (MinijarFilter.java:104)
at org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters (ShadeMojo.java:992)
at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute (ShadeMojo.java:521)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:565)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

I do think that the failing IT comes from different things, especially the combination of: compiling against Java 1.6, using JUnit 3 and Maven 3.6.3.
Or do you have another idea? @slawekjaranowski