Exit Windows scripts promptly on failure

Browse Source

When invoking the elasticsearch-env.bat or x-pack-env.bat batch scripts
on Windows, if these scripts exits due to an error (e.g., Java can not
be found, or the wrong version of Java is found), then the script
exits. Sadly, on Windows, this does not also terminate the caller,
instead returning control. This means we have to explicitly exit so that
is what we do in this commit.

Relates elastic/x-pack-elasticsearch#2126

Original commit: elastic/x-pack-elasticsearch@18645db62c

...

This commit is contained in:

Jason Tedor 2017-07-31 20:39:59 +09:00 committed by GitHub

parent 50b8a56d34

commit a80b1e4de1

7 changed files with 0 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN

plugin/bin/x-pack/certgen.bat

Binary file not shown.

BIN

plugin/bin/x-pack/croneval.bat

Binary file not shown.

BIN

plugin/bin/x-pack/extension.bat

Binary file not shown.

BIN

plugin/bin/x-pack/migrate.bat

Binary file not shown.

BIN

plugin/bin/x-pack/setup-passwords.bat

Binary file not shown.

BIN

plugin/bin/x-pack/syskeygen.bat

Binary file not shown.

BIN

plugin/bin/x-pack/users.bat

Binary file not shown.