Thanks for pointing out the standard NAR bundles, Mark. There are a number
of components in the standard NAR bundles with particular dependencies that
would make more sense in separate NARs. Reorganizing the standard NAR to
components with limited dependencies and wide applicability would
There’s also some code that exists in order to maintain backward compatibility
in the repositories. I would very much like the repositories to contain no
unnecessary code. And swap file format supports really old formats. And the old
impls of the repositories themselves, like PersistentProvRepo
Russell,
AFAICT from looking at Elastic's repos, the low level REST client is
still fine.
https://github.com/elastic/elasticsearch/blob/e5518e07f13701e3bb3dcc6842b9023966752497/client/rest/src/main/java/org/elasticsearch/client/RestClient.java
Our Elasticsearch support is spread over two NARs
