ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-12113) control.sh terminates silently when JAVA_HOME is not set
Date Tue, 27 Aug 2019 16:29:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexey Goncharuk updated IGNITE-12113:
--------------------------------------
    Attachment: IGNITE-12113_Fix_silent_control_sh_fail_when_JAVA_HOME_is_empty.patch

> control.sh terminates silently when JAVA_HOME is not set
> --------------------------------------------------------
>
>                 Key: IGNITE-12113
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12113
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.8, 2.7.6
>
>         Attachments: IGNITE-12113_Fix_silent_control_sh_fail_when_JAVA_HOME_is_empty.patch
>
>
> Running control.sh from ignite-2.7.6 release candidate on MacOS with empty JAVA_HOME
produces no output - the script terminates without any action.
> The reason is the following line in {{bin/control.sh}}:
> {code}
> javaMajorVersion "${JAVA_HOME}/bin/java"
> {code}
> Since {{JAVA_HOME}} is empty, the argument passed to the function is invalid and the
function terminates the script. I suggest replacing the {{${JAVA_HOME}/bin/java}} with just
{{$JAVA}} because it is already determined earlier in the scope. The suggested fix works in
my environment for all options of {{JAVA_HOME}}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message