Is the version of elasticsearch version of Guice different from 3.0? Same
question for the other libs that are in elasticsearch.
Now that elasticsearch supports Maven, would it make sense not to bundle
code that is unchanged in elasticsearch?
Having theses libs embedded in ES lets developpers use their own version of useful libs without classloading issues.
See here : http://groups.google.com/a/elasticsearch.com/group/users/msg/6449836b9631fee6
HTH
David 
@dadoonet
Le 14 févr. 2012 à 01:33, Derrick derrickrburns@gmail.com a écrit :
Is the version of elasticsearch version of Guice different from 3.0? Same question for the other libs that are in elasticsearch.
Now that elasticsearch supports Maven, would it make sense not to bundle code that is unchanged in elasticsearch?
On Feb 13, 4:33 pm, Derrick derrickrbu...@gmail.com wrote:
Now that elasticsearch supports Maven, would it make sense not to bundle
code that is unchanged in elasticsearch?
It would, but only for people running elasticsearch in an OSG
environment. You wouldn't want to be forced to use the same version of
the libraries that elasticsearch happens to use...
elasticsearch uses guice 2.0, and its a modified version than the one provided (mainly to reduce its memory footprint). Once, before even using Guice 2.0 embedded codebase, we upgraded to 3.0 and it used even more memory and was considerable slower. As far as Guice is concerned, its now part of elasticsearch and is considered internal (but can be used by plugins).
On Tuesday, February 14, 2012 at 9:09 AM, Eric Jain wrote:
On Feb 13, 4:33 pm, Derrick <derrickrbu...@gmail.com (http://gmail.com)> wrote:
Now that elasticsearch supports Maven, would it make sense not to bundle
code that is unchanged in elasticsearch?It would, but only for people running elasticsearch in an OSG
environment. You wouldn't want to be forced to use the same version of
the libraries that elasticsearch happens to use...