You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/04/06 17:22:00 UTC

[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.

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

Vyacheslav Koptilin updated IGNITE-16601:
-----------------------------------------
    Epic Link: IGNITE-16807

> The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-16601
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16601
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 3.0.0-alpha4
>            Reporter: Fedor Malchikov 
>            Priority: Blocker
>              Labels: ignite-3, ignite-3-cli-tool
>
> As a result, working on environments where java is not directly installed or several versions of java are used is significantly complicated. As far as I know, in version 2, overriding java_home was the main method of switching between java versions in the system.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)