Github user neykov commented on the pull request:
https://github.com/apache/brooklyn-server/pull/56#issuecomment-197808496
Re guava version change - haven't looked at the specific API changes
between versions, but would expect that they would lead to a compile error if
something used by Brooklyn changed. Will take a look at the release notes to
confirm.
I suggest that we follow the jclouds lead and stick to the least common
denominator API between guava versions. Then we can leave the v17 dependency in
the pom, but load 16-18 in Karaf, as we see fit.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---