33785e5446
Currently, running any task while attached to elasticsearch will also try to run that task in all elasticsearch projects. This change causes x-plugins to be moved into a subproject when attached. It does this by dynamically creating a fake root project, and making this root project think it is attached to the existing attachments, along with x-plugins itself. This also fixes buildSrc so attachment to elasticsearch's buildSrc actually works. Original commit: elastic/x-pack-elasticsearch@da0adf1da5 |
||
|---|---|---|
| buildSrc | ||
| marvel | ||
| qa | ||
| shield | ||
| watcher | ||
| x-dev-tools | ||
| .dir-locals.el | ||
| .projectile | ||
| LICENSE.txt | ||
| README.asciidoc | ||
| build.gradle | ||
| settings.gradle | ||
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.