On Thu, 7 Aug 2014, Andreas Beeker wrote:
In the discussion of having new features (incl. new dependencies) and
not to have them, mostly the second part wins, as "POI is included in
quite some other projects where the new dependency (version) could
interfere".
I think, at least for the test stuff, this shouldn't be a problem ...
I know it might not be quite such fun, but I'd vote for trying guava out
on tests first. Adding a new dependency to core is a potentially big deal,
with large effects on most of our downstream users. Adding dependencies to
test is fairly easy.
If we could start out with some improvements to tests with Guava, that'll
help everyone see the benefits, and get comfortable with it, without
impacting users. That will also mean that if we do all decide to roll it
out to the main code too, we've a strong case to use to justify it to
those users who complain (and trust me, there will be a number of users
who'll complain...)
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
