🔎 Open source distributed and RESTful search engine.
Go to file
Ryan Ernst 0d67caa468 Build: Clean buildSrc on gradle clean
Same change as elastic/elasticsearchelastic/elasticsearch#14785 but for xplugins.

Original commit: elastic/x-pack-elasticsearch@02e8247686
2015-11-16 12:45:03 -08:00
buildSrc Build: Improve behavior and setup for attachment to elasticsearch 2015-11-06 11:08:03 -08:00
marvel Checks the number of actions in bulk request 2015-11-16 15:57:18 +01:00
qa Remove confusing pom.xml files 2015-11-05 10:39:28 -05:00
shield Fix compilation errors with org.elasticsearch.cluster.health.ClusterHealthStatus 2015-11-16 15:34:26 +01:00
watcher Fixing references to bin/plugin -i 2015-11-12 13:45:38 -05:00
x-dev-tools Remove confusing pom.xml files 2015-11-05 10:39:28 -05:00
.dir-locals.el Add .dir-locals.el and .projectile 2015-10-30 11:16:29 -06:00
.projectile Add .dir-locals.el and .projectile 2015-10-30 11:16:29 -06:00
LICENSE.txt Initial X-Pack commit 2018-04-20 14:16:58 -07:00
README.asciidoc Add attachment docs to README 2015-11-04 11:19:13 -08:00
build.gradle Build: Clean buildSrc on gradle clean 2015-11-16 12:45:03 -08:00
settings.gradle Fix build to still work when not attached to elasticsearch 2015-11-06 14:03:08 -08:00

README.asciidoc

= Elasticsearch X Plugins

A set of Elastic's commercial plugins:

- License
- Shield
- Watcher
- Marvel

= Testing with Elasticsearch
Sometimes it is useful to use your local elasticsearch checkout with x-plugins. To do this, run the following commands:
cd buildSrc
gradle attach --name elasticsearch --path /path/to/elasticsearch/buildSrc
cd ..
gradle attach --name elasticsearch --path /path/to/elasticsearch

This will cause building x-plugins to reflect any changes in your elasticsearch repo. For example, if you make a change to elasticsearch core, building x-plugins will first re-build elasticsearch core, and use that when building x-plugins.