Alix Lourme created MNG-6648:
--------------------------------
Summary: Add command line parameters in 'mavenrc_pre' script
Key: MNG-6648
URL: https://issues.apache.org/jira/browse/MNG-6648
Project: Maven
Issue Type: Improvement
Components: Command Line
Affects Versions: 3.6.1, 3.6.0
Reporter: Alix Lourme
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|https://maven.apache.org/docs/3.3.1/release-notes.html#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):
{code}
if exist "%USERPROFILE%\mavenrc_pre.cmd" call "%USERPROFILE%\mavenrc_pre.cmd %*"
{code}
It's allow any user customization, using Maven standards.
If relevant, I can provide PR.
Best regards
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
