[
https://issues.apache.org/jira/browse/STORM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950034#comment-13950034
]
Adam Lewis commented on STORM-268:
----------------------------------
Curator is using it. v11 as of netflix curator 1.3.3, v14 for apache curator
master/HEAD ... so simply taking the dependency out of the storm pom would
actually represent a guava downgrade. Of course, it could always be managed to
v16 by storm assuming there are no issues with curator.
> Update guava to v16
> -------------------
>
> Key: STORM-268
> URL: https://issues.apache.org/jira/browse/STORM-268
> Project: Apache Storm (Incubating)
> Issue Type: Dependency upgrade
> Affects Versions: 0.9.2-incubating
> Reporter: Simon Cooper
> Priority: Minor
>
> Storm currently uses guava 13, released August 2012. There are several things
> I would like to use in the latest release (v16) in my topology code, as well
> as various performance improvements and bug fixes. Could the storm dependency
> on guava be upgraded to v16.0.1?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
