[MNG-6648] 'mavenrc_pre' script does not receive arguments like mavenrc in Bourne shell does

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0, 3.6.1
• Fix Version/s: 3.8.2, 4.0.0-alpha-2, 4.0.0
• Component/s: Command Line
• Labels: command-line script
• Assignee: Michael Osipov
• Reporter: Alix Lourme
• Created: 25/Apr/19 15:07
• Updated: 20/Oct/22 08:11
• Resolved: 23/Jul/21 18:10

Description

Hello,

In some corner-case, you could have to run Maven with a custom JAVA_HOME (JDK v8, v11, ... even if it is evil some plugin can be impacted by JDK at runtime).

If it is per-project, JVM and Command Line Options is not relevant and update JAVA_HOME each time in your environment could be boring.

A command line user-custom-parameter (ex : -Dmy.jdk=11) could be simple to achieve that.

A Maven script wrapper could be implemented for that, but it's like update the Maven distribution => evil.
The mavenrc_pre (MNGSITE-246) could be perfect for that feature !
But currently command line parameters are not used in script .

If parameters are used dor script call, sample for mvn.cmd (windows):

if exist "%USERPROFILE%\mavenrc_pre.cmd" call "%USERPROFILE%\mavenrc_pre.cmd %*"

It's allow any user customization, using Maven standards.

If relevant, I can provide PR.
Best regards

Issue Links

• is related to: MWRAPPER-27 rework mvnw* scripts to better match mvn* from Maven 3.8
• links to: GitHub Pull Request #511