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)
I don’t know if this is expected, but this change breaks running Maven through IntelliJ. Indeed it invokes Maven through
javawithout settingmaven.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.
Originally posted by @DidierLoiseau in #1750 (comment)