OpenSearch/plugin/bin/x-pack
Jason Tedor a80b1e4de1 Exit Windows scripts promptly on failure
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
2017-07-31 20:39:59 +09:00
..
certgen Pass config path as a system property 2017-07-28 12:15:37 +09:00
certgen.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
croneval Pass config path as a system property 2017-07-28 12:15:37 +09:00
croneval.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
extension Pass config path as a system property 2017-07-28 12:15:37 +09:00
extension.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
migrate Pass config path as a system property 2017-07-28 12:15:37 +09:00
migrate.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
setup-passwords Pass config path as a system property 2017-07-28 12:15:37 +09:00
setup-passwords.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
syskeygen Pass config path as a system property 2017-07-28 12:15:37 +09:00
syskeygen.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
users Pass config path as a system property 2017-07-28 12:15:37 +09:00
users.bat Exit Windows scripts promptly on failure 2017-07-31 20:39:59 +09:00
x-pack-env Use elasticsearch-env 2017-07-21 09:39:46 +09:00