# Replacement for obsolete libraries when writing plugins?

**URL:** <https://discuss.elastic.co/t/replacement-for-obsolete-libraries-when-writing-plugins/99069>\
**Category:** Elasticsearch\
**Created:** [September 1, 2017, 12:08am UTC](https://discuss.elastic.co/t/replacement-for-obsolete-libraries-when-writing-plugins/99069 "2017-09-01T00:08:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chaoism](https://avatars.discourse-cdn.com/v4/letter/c/958977/32.png) [@chaoism](https://discuss.elastic.co/u/chaoism)\
**Post date:** [September 1, 2017, 12:08am UTC](https://discuss.elastic.co/t/replacement-for-obsolete-libraries-when-writing-plugins/99069/1 "2017-09-01T00:08:51Z")

</div>

I have an existing plugin for a custom analyzer, but it is built for ES 1.x

Some of the libraries it imports are obsolete. I'm wondering if there are replacements for these libraies

So far, I need to replace:

- org.elasticsearch.index.IndexSettings
- org.elasticsearch.index.analysis.AnalysisModule.AnalysisBinderProcessor

And in general, if ES stops supports certain libraries, how would people deal with it?

---

<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:** [September 29, 2017, 12:09am UTC](https://discuss.elastic.co/t/replacement-for-obsolete-libraries-when-writing-plugins/99069/2 "2017-09-29T00:09:30Z")

</div>

Closed on September 29, 2017, 12:09am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.