https://bugzilla.redhat.com/show_bug.cgi?id=902086 --- Comment #55 from Jörg Prante <joergprante@xxxxxxxxx> --- Each Elasticsearch version is tied to exact versions in the dependencies. Please note that it is important to use exactly the version of an Elasticsearch dependency as stated in the pom.xml One reason is, Elasticsearch uses shaded dependencies, which might not work with different versions. For example, Netty is shaded. Other reason is, Elasticsearch might contain some (rare) fixes to existing classes in the dependencies that are not in the upstream. This is implemented by setting the elasticsearch.jar always in front of the other dependent jars to override them (for instance, Lucene, Guava, Joda, just to name the most important). Also, more reasons are compatibility issues, e.g. Elasticsearch is strictly aligned to features in the corresponding Lucene version, and maybe other jars. The integration tests of Elasticsearch should be executed with success to reveal such problems in the build process. If you ignore integration testing and use other versions as defined by Elasticsearch, Elasticsearch might not work as expected, and Elasticsearch might throw obscure errors and exceptions later at runtime. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review