# Why the third party dependency repackaging?

**URL:** <https://discuss.elastic.co/t/why-the-third-party-dependency-repackaging/3502>\
**Category:** Elasticsearch\
**Created:** [November 2, 2010, 3:53pm UTC](https://discuss.elastic.co/t/why-the-third-party-dependency-repackaging/3502 "2010-11-02T15:53:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael\_c\_small](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@michael\_c\_small](https://discuss.elastic.co/u/michael_c_small)\
**Post date:** [November 2, 2010, 3:53pm UTC](https://discuss.elastic.co/t/why-the-third-party-dependency-repackaging/3502/1 "2010-11-02T15:53:42Z")

</div>

Why does the build process for elasticsearch repackage third party APIs (e.g. joda) into elasticsearches namespace? From a user's point of view, should I use the repackaged elasticsearch APIs (e.g. org.elasticsearch.common.joda.time.DateTime or should I just simple use org.joda.time.DateTime). Sorry, I've just never seen a project structured in such a way.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:17am UTC](https://discuss.elastic.co/t/why-the-third-party-dependency-repackaging/3502/2 "2017-07-06T04:17:18Z")

</div>

Closed on July 6, 2017, 4:17am UTC