Thank for feedback.
Nothing we can't do with our code :) Guava is just 'facilities' make code more 
clear, shorter and sometime faster.
I agree that this integration brings more dependencies, may create conflicts in 
end-users applications. Leave as it for now.

Cheers,

Hong-Thai

-----Message d'origine-----
De : Jukka Zitting [mailto:jukka.zitt...@gmail.com] 
Envoyé : jeudi 6 mars 2014 16:47
À : Tika Development
Objet : Re: Using guava on tika ?

Hi,

On Thu, Mar 6, 2014 at 6:54 AM, Nick Burch <apa...@gagravarr.org> wrote:
> On Thu, 6 Mar 2014, Hong-Thai Nguyen wrote:
>> Guava (https://code.google.com/p/guava-libraries/) provides many 
>> facilities on text, file, collection ... manipuation. Should we use in Tika?
>
> Can you give an example of where using Guava would either simplify 
> some existing code, or improve its effectiveness, or permit something 
> we couldn't otherwise do?

Also, especially in tika-core we've explicitly avoided any external 
dependencies to keep it as simple and easy as possible to include as a 
dependency in client applications. We've even gone as far as including copies 
of some Commons IO classes in org.apache.tika.io instead of referring to 
commons-io as a dependency.

BR,

Jukka Zitting

Reply via email to