You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2015/04/09 17:40:12 UTC

[jira] [Resolved] (IGNITE-704) Windows shell scripts don't process NO_PAUSE environment variable

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

Alexey Kuznetsov resolved IGNITE-704.
-------------------------------------
    Resolution: Fixed
      Assignee: Sergey Kozlov  (was: Alexey Kuznetsov)

Test in branch ignite-704.

After investigation I found that it is expected behaviour.

ignite.bat and ignitevisorcmd.bat support several commandline options like "-v"

And there is special option "-np" that control pause or not after ignite.bat(ignitevisorcmd.bat) finished.

So, I added information about this option into --help option for ignite.bat.
And implemented support for --help option for ignitevisorcmd.bat

To test: execute
 ignite.bat --help
 ignitevisorcmd.bat --help
 ignite.bat -np
 ignitevisorcmd.bat -np



> Windows shell scripts don't process NO_PAUSE environment variable
> -----------------------------------------------------------------
>
>                 Key: IGNITE-704
>                 URL: https://issues.apache.org/jira/browse/IGNITE-704
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: sprint-3
>            Reporter: Sergey Kozlov
>            Assignee: Sergey Kozlov
>            Priority: Minor
>             Fix For: sprint-3
>
>
> bin\ignite.bat
> bin\ignitevisorcmd.bat
> Both scripts above has following code:
> {noformat}
> if not "%NO_PAUSE%" == "1" pause
> {noformat}
> But really set  NO_PAUSE=0 has no affect to script. It seems the variable redefined somewhere in script



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)