# Getting Jar Hell

**URL:** <https://discuss.elastic.co/t/getting-jar-hell/115423>\
**Category:** Elasticsearch\
**Created:** [January 13, 2018, 11:34pm UTC](https://discuss.elastic.co/t/getting-jar-hell/115423 "2018-01-13T23:34:22Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 14, 2018, 2:24pm UTC](https://discuss.elastic.co/t/getting-jar-hell/115423/12 "2018-01-14T14:24:53Z")

</div>

> I want to start test elasticsearch instance from java code for my tests.

It's not supported. See [Elasticsearch, the server | Elastic Blog](https://www.elastic.co/blog/elasticsearch-the-server)

Read this for some options:

> [@In memory testing with RestHighLevelClient](https://discuss.elastic.co/t/in-memory-testing-with-resthighlevelclient/106196/6):
>
> This will not happen. To do integration tests, you can: Use the Gradle tools elasticsearch already has. You can read some information about this here: [#21119](https://github.com/elastic/elasticsearch/issues/21119). This [sample project](https://github.com/joel-costigliola/elastic-search-test) shows how to use Elasticsearch Test Classes Use the Maven plugin: [GitHub - alexcojocaru/elasticsearch-maven-plugin: A Maven plugin to run a single node Elasticsearch cluster during the integration test phase of a build](https://github.com/alexcojocaru/elasticsearch-maven-plugin) Use Ant scripts like [https://david.pilato.fr/blog/2016-07-29-elasticsearch-real-integration-tests/](http://david.pilato.fr/blog/2016/10/18/elasticsearch-real-integration-tests-updated-for-ga/) …

---

_[View the full topic](https://discuss.elastic.co/t/getting-jar-hell/115423)._
