🔎 Open source distributed and RESTful search engine.
Go to file
Alexander Reelsen aa77646e3d Tests: Fixing xpack info tests
Even though HEAD is a possible method, this implies that no data is returned
and thus the tests fail randomly.

If HEAD should be added to the api it needs it's own API definition IMO.

Original commit: elastic/x-pack-elasticsearch@a216393f6b
2016-04-18 12:19:16 +02:00
buildSrc Build: Change x-plugins setup with elasticsearch to a sibling directory 2015-11-23 14:20:48 -08:00
dev-tools test: update the ci script 2016-04-07 08:34:58 -04:00
elasticsearch Tests: Fixing xpack info tests 2016-04-18 12:19:16 +02:00
.dir-locals.el Update .dir-locals.el for enforced line length 2016-02-04 14:55:41 -07:00
.projectile Add .dir-locals.el and .projectile 2015-10-30 11:16:29 -06:00
GRADLE.CHEATSHEET Create GRADLE.CHEATSHEET 2015-11-24 21:02:28 +01:00
LICENSE.txt Initial X-Pack commit 2018-04-20 14:16:58 -07:00
README.asciidoc update setup instructions 2016-01-08 07:31:54 -05:00
build.gradle build: fix x-pack pom and allow installation 2016-04-15 11:31:09 -04:00
gradle.properties Gradle daemon is a demon 2015-11-25 10:39:08 -05:00
settings.gradle Build: Change x-plugins setup with elasticsearch to a sibling directory 2015-11-23 14:20:48 -08:00

README.asciidoc

= Elasticsearch X Plugins

A set of Elastic's commercial plugins:

- License
- Shield
- Watcher
- Marvel

= Setup
You must checkout x-plugins and elasticsearch in the same directory as siblings. This
elasticsearch checkout will be used when building x-plugins.