Hi Brian, Le 07/01/2014 15:40, Brian Demers a écrit :
I agree with Les with being cautious about long term support.
I totally agree with you, any code commited should be viewed as the long term cost of its maintenance. We are talking of single class, so i think there won't be any maintenance to do.
Also, Guava cache API is no longer annotated @Beta so the API should not change so it's now safe to consider the maintenance cost will be minor.
> However, I
noticed we do not have a 'third-party' library page. (Lots of projects do this, but here is an example that sticks out in my mind: http://metrics.codahale.com/manual/third-party/) I think this would fit for a page like that (at least initially)
If we don't integrate support in Shiro, i will publish it on nuiton.org, it's a forge for java libraries maintained by my company which nexus repo is synchronized on central.
My company/nuiton.org policy is to publish under LGPL so it may be a concern. I may ask to my company to publish under the same license as Shiro.
A third-party page is good idea :) Thanks for your answer. -- Brendan Le Ny, Code Lutin [email protected] (+33) 02 40 50 29 28
