Get rid of external dependencies like guava

[GoogleCodeExporter]

Reflections brings in a few of its own transitive dependencies, like guava. 
Guava is a pretty popular library, so this will likely lead to conflicts in 
projects that require incompatible versions of guava.

Other library projects generally use jarjar or proguard if they really want to 
use stuff like guava. I suggest doing something similar. Or don't use guava.

Currently a work-around is to purposely <exclude> the guava dependency.

Original issue reported on code.google.com by james.r...@gmail.com on 31 May 2012 at 4:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Depending on which bits of Guava are used by Reflections, you may find that you 
can drop the version that Reflections depends on (say to 10) and that way, if 
another project that uses Reflections also uses a newer version of Guava, Maven 
(or whatever dependency resolution system you're using) should pick the newest 
version automatically.

This doesn't remove the problem entirely but will mitigate it for users who are 
still on Guava 10. You won't be able to use Reflections if you <exclude> Guava 
and include instead an older version. (If you can in fact do this then 
Reflections needs to depend on that version rather than v11.)

Original comment by jonnyt...@gmail.com on 26 Aug 2012 at 2:18

[GoogleCodeExporter]

guava is part of reflections. upgraded version to 15.0, still binary compatible 
with 10.0+. see https://code.google.com/p/reflections/issues/detail?id=164

Original comment by ronm...@gmail.com on 21 Dec 2013 at 9:32

• Changed state: Fixed