Guava dependency - to drop or not to drop?

[Lukáš Fryč]

That's a valid concern,

----

It leaves us only with one option:

* get rid of the deprecated Beta APIs (PR sent, thanks Cody!)
* upgrade to 16.x

We could:

* get rid of APIs as we upgrade to newer Java
* get rid of APIs we do use sparely and for no reason (e.g. just once or
twice) (e.g. MapMaker)


----

Some of other APIs we use and are still @Beta in 16:

2x ByteStreams (@Beta, but Since Guava 1.0)
1x Files (@Beta, but Since Guava 1.0)
4x LoadingCache (@Beta, Since Guava 11.0)

The last one is the only which is potentially fragile (we already had to
refactor it once):
https://github.com/richfaces/richfaces/commit/9f26b20e1850548f683fd406146216e25c0ab4e1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/richfaces-dev/attachments/20140218/e28b2c85/attachment.html