Why elasticsearch has separate JNA library


Why do we maintain separate JNA library for elasticsearch?
Found this repo in maven dependency: https://mvnrepository.com/artifact/org.elasticsearch/jna

See https://github.com/elastic/jna-build - support for some platforms has been removed.


Thanks for the help!

There's a need to use the Original JNA library for my project. What are the problems that are most likely to come up if I use the default JNA library?

The primary motivation to create our own build of JNA was inconsistency in the compatibility of artifacts produced by the JNA project. By building our own, we ensure that the operating systems we support are all supported, regardless of which random (!) OS/system built the artifacts for a JNA release. Using the original JNA might work, but it is not supported, and doing so would mean replacing a jar within Elasticsearch, which will eventually become an error.

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