Unable to launch Maven: org.codehaus.plexus.classworlds.launcher.ConfigurationException: No such property: maven.mainClass

[gnodet]

I don’t know if this is expected, but this change breaks running Maven through IntelliJ. Indeed it invokes Maven through java without setting maven.mainClass. Is it expected that all tools which do that will have to add this argument, specifying the main class?

Also note that the exception is a bit confusing since it does not say where this property is being used.

/home/didier/.sdkman/candidates/java/22-open/bin/java -Dmaven.multiModuleProjectDirectory=… -Djansi.passthrough=true -Dmaven.home=/home/didier/.sdkman/candidates/maven/master -Dclassworlds.conf=/home/didier/.sdkman/candidates/maven/master/bin/m2.conf -Dmaven.ext.class.path=/home/didier/.local/share/JetBrains/Toolbox/apps/intellij-idea-community-edition-3/plugins/maven/lib/maven-event-listener.jar -javaagent:/home/didier/.local/share/JetBrains/Toolbox/apps/intellij-idea-community-edition-3/lib/idea_rt.jar=38433:/home/didier/.local/share/JetBrains/Toolbox/apps/intellij-idea-community-edition-3/bin -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -classpath /home/didier/.sdkman/candidates/maven/master/boot/plexus-classworlds.license:/home/didier/.sdkman/candidates/maven/master/boot/plexus-classworlds-2.8.0.jar org.codehaus.classworlds.Launcher -Didea.version=2024.3 validate
org.codehaus.plexus.classworlds.launcher.ConfigurationException: No such property: maven.mainClass
	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.filter(ConfigurationParser.java:355)
	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:114)
	at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:123)
	at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:116)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:356)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:41)

Process finished with exit code 100

Originally posted by @DidierLoiseau in #1750 (comment)

[gnodet]

The problem can also be easily reproduced by running the Maven Wrapper ITs with Maven 4.0.0-rc-4:

[INFO] [stdout] [INFO] Apache Maven Wrapper 3.3.3-SNAPSHOT
Warning:  [stderr] org.codehaus.plexus.classworlds.launcher.ConfigurationException: No such property: maven.mainClass
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.filter(ConfigurationParser.java:398)
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:121)
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:123)
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:116)
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:356)
Warning:  [stderr] 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
Warning:  [stderr] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Warning:  [stderr] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
Warning:  [stderr] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Warning:  [stderr] 	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
Warning:  [stderr] 	at org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:52)
Warning:  [stderr] 	at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:161)
Warning:  [stderr] 	at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:73)