You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/07/19 23:03:00 UTC

[jira] [Created] (MNG-7192) Remove unsed MAVEN_CMD_LINE_ARGS environment variable MAVEN_CONFIG in startup scripts

Michael Osipov created MNG-7192:
-----------------------------------

             Summary: Remove unsed MAVEN_CMD_LINE_ARGS environment variable MAVEN_CONFIG in startup scripts
                 Key: MNG-7192
                 URL: https://issues.apache.org/jira/browse/MNG-7192
             Project: Maven
          Issue Type: Task
          Components: Command Line
            Reporter: Michael Osipov


It has been introduced in 70218af1c1824caa892e7e507463ea713faa7133

This environment variable has several issues:

* Its usage has already been reduced: https://github.com/apache/maven/commit/27eabec6c6b311d3b24eb2d5752634d9811f9f51, https://github.com/apache/maven/commit/6d304204389af94b75aa26cf30c7eb5bc90279ea, https://github.com/apache/maven/commit/27eabec6c6b311d3b24eb2d5752634d9811f9f51, https://github.com/apache/maven/commit/7589e43f57125ee078aeec15d3f2d62360727a57
* Is is not consistently used between Bourne shell script and Windows command script
* It breaks arguments/options with spaces in the Bourne shell script
* It is not used in any of our plugins according to the GitHub search in the apache organization
* It is not realiable possible to break this up again in single args because of whitespaces and incompatible quoting rules between Windows and POSIX, thus requires non-portable Java code



--
This message was sent by Atlassian Jira
(v8.3.4#803005)