Fix maven.mainClass property missing for external tools#10998
Merged
gnodet merged 1 commit intoapache:masterfrom Jul 28, 2025
Merged
Fix maven.mainClass property missing for external tools#10998gnodet merged 1 commit intoapache:masterfrom
gnodet merged 1 commit intoapache:masterfrom
Conversation
Fixes apache#10996 When external tools like IntelliJ launch Maven directly using the ClassWorlds launcher without setting the maven.mainClass system property, Maven fails with 'No such property: maven.mainClass'. This change adds a default value for maven.mainClass in m2.conf so that external tools can launch Maven without needing to know about this property. The default value is org.apache.maven.cling.MavenCling which is the standard Maven CLI entry point. The fix maintains backward compatibility - Maven launcher scripts continue to work normally by setting the property explicitly, while external tools now have a sensible default.
elharo
approved these changes
Jul 26, 2025
Contributor
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
gnodet
added a commit
to gnodet/maven
that referenced
this pull request
Jul 28, 2025
Fixes apache#10996 When external tools like IntelliJ launch Maven directly using the ClassWorlds launcher without setting the maven.mainClass system property, Maven fails with 'No such property: maven.mainClass'. This change adds a default value for maven.mainClass in m2.conf so that external tools can launch Maven without needing to know about this property. The default value is org.apache.maven.cling.MavenCling which is the standard Maven CLI entry point. The fix maintains backward compatibility - Maven launcher scripts continue to work normally by setting the property explicitly, while external tools now have a sensible default. (cherry picked from commit 4e50e95)
gnodet
added a commit
that referenced
this pull request
Aug 5, 2025
) Fixes #10996 When external tools like IntelliJ launch Maven directly using the ClassWorlds launcher without setting the maven.mainClass system property, Maven fails with 'No such property: maven.mainClass'. This change adds a default value for maven.mainClass in m2.conf so that external tools can launch Maven without needing to know about this property. The default value is org.apache.maven.cling.MavenCling which is the standard Maven CLI entry point. The fix maintains backward compatibility - Maven launcher scripts continue to work normally by setting the property explicitly, while external tools now have a sensible default. (cherry picked from commit 4e50e95)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #10996
When external tools like IntelliJ launch Maven directly using the ClassWorlds launcher without setting the
maven.mainClasssystem property, Maven fails with:Root Cause
The m2.conf file was changed to use
${maven.mainClass}but this property is only set by the Maven launcher scripts (mvnandmvn.cmd). External tools that launch Maven directly don't set this property.Solution
This change adds a default value for
maven.mainClassin m2.conf:How it works
-Dmaven.mainClass=org.apache.maven.cling.MavenCling(or other variants for--enc,--shell,--up)org.apache.maven.cling.MavenClingis the standard Maven CLI entry pointImpact
mvnscriptsmaven.mainClasspropertyThe solution uses the same ClassWorlds configuration syntax already used elsewhere in the m2.conf file (
set maven.conf default ${maven.home}/conf).Pull Request opened by Augment Code with guidance from the PR author