ES 2.0.0 + Antlr4 = Jar Hell

Elastic Stack Elasticsearch
1

It appears I can neither write an ES 2.0 plugin nor an application that uses a Node Client if I also want to use Antlr4 in my plugin or application, due to a "jar hell" IllegalStateException indicating a conflict with ES's antlr-runtime-3.5.jar.

Is there any way around this, or do I need to suck it up and use Antlr3 instead of Antlr4?

2

If you don't use the Lucene Expression Language

https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html#_lucene_expressions_scripts

(which is optional to ES 2.0) you can safely remove ES antlr-runtime-3,5.jar