[
https://jira.codehaus.org/browse/MNG-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5579:
--------------------------------
Description:
Currently,
both output two different messages.
Shell:
{quote}
Error: JAVA_HOME is not defined correctly.
We cannot execute $JAVACMD
{quote}
while batch says:
{quote}
Error: JAVA_HOME not found in your environment.
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.
{quote}
Same applies for {{M2_HOME}}. Additionally, testing for the Java command is
handled different in both scripts. The batch script relies on JAVA_HOME while
the shell script can ignore it. Both should require {{JAVA_HOME}} or warn about
and use {{which java}}, respectively {{java}} in {{PATH}} on Windows. After
that should proceed to checking {{M2_HOME}}.
Any thoughts?
was:
Currently,
both output two different messages.
Shell:
{quote}
Error: JAVA_HOME is not defined correctly.
We cannot execute $JAVACMD
{quote}
while batch says:
{quote}
Error: JAVA_HOME not found in your environment.
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.
{quote}
Same applies for {{M2_HOME}}. Additionally, testing for the Java command is
handled different in both scripts. The batch script relies on JAVA_HOME while
the shell script can ignore it. Both should require {{JAVA_HOME}} or warn about
and use {{which java}}, respectively {{java}} in {{PATH}} on Windows. After
that should proceed to checking {{M2_HOME}}.
> Unify error output/check logic from shell and batch scripts
> -----------------------------------------------------------
>
> Key: MNG-5579
> URL: https://jira.codehaus.org/browse/MNG-5579
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.1.1
> Reporter: Michael Osipov
> Priority: Minor
>
> Currently,
> both output two different messages.
> Shell:
> {quote}
> Error: JAVA_HOME is not defined correctly.
> We cannot execute $JAVACMD
> {quote}
> while batch says:
> {quote}
> Error: JAVA_HOME not found in your environment.
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
> {quote}
> Same applies for {{M2_HOME}}. Additionally, testing for the Java command is
> handled different in both scripts. The batch script relies on JAVA_HOME while
> the shell script can ignore it. Both should require {{JAVA_HOME}} or warn
> about and use {{which java}}, respectively {{java}} in {{PATH}} on Windows.
> After that should proceed to checking {{M2_HOME}}.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
