Add plugins from classpath in embedded Elasticsearch client node

Thanks for your reply!

This is basically what I'm doing right now:

For the time being I "cheated" a little bit by creating a sub-class of Node which exposes the constructor which allows passing a collection of plugin classes to be loaded on startup, but this feels kind of dirty.

The question is, if this is the intended way to do it.