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
..
bin/x-pack	Exit Windows scripts promptly on failure	2017-07-31 20:39:59 +09:00
bwc	Remove assemble from build task when assemble removed	2017-06-16 17:19:47 -04:00
config/x-pack	Rename core plugin and transport dirs	2017-02-10 11:02:42 -08:00
keys	Rename core plugin and transport dirs	2017-02-10 11:02:42 -08:00
licenses	Use shaded rest client dependencies	2017-07-24 12:56:17 -05:00
ml-cpp-snapshot	Build: Switch ml snapshot dependency to a local project (elastic/x-pack-elasticsearch#1559)	2017-05-26 01:15:12 -07:00
src	[Security] Add 'read_cross_cluster' privilege for .monitoring indices (elastic/x-pack-elasticsearch#2111)	2017-07-28 16:02:20 -04:00
.gitignore	Remove QueryParseContext (elastic/x-pack-elasticsearch#1895)	2017-07-03 17:31:18 +02:00
build.gradle	Move tribe to a module (elastic/x-pack-elasticsearch#2088)	2017-07-28 11:23:52 +02:00