Hi Brian,

I think I'm missing something.
At the end you still have the full elasticsearch jars, right?
What is the difference with having that as a maven dependency?

Is it a way for not getting all elasticsearch dependencies which are shaded in 
elasticsearch jar such as Jackson, Guice,... ?

David

> Le 14 nov. 2014 à 23:38, Brian <[email protected]> a écrit :
> 
> Filip,
> 
> Or, just put all of the Elasticsearch jars on your local client system, then 
> add their containing directory (with "/*" appended to it) to your -classpath, 
> and your client can use the TransportClient. Java will pull in exactly what 
> it needs and nothing it doesn't. And your client code stays tiny. Works great 
> for us!
> 
> Brian
> -- 
> You received this message because you are subscribed to the Google Groups 
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/2fe6afa7-6ff0-4ed6-8792-1909f3ecc3d2%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/274D159D-2BE9-45A2-82A9-C0BFD5BB4460%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Reply via email to