[
https://issues.apache.org/jira/browse/CURATOR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045800#comment-16045800
]
ASF GitHub Bot commented on CURATOR-417:
----------------------------------------
Github user ajayk commented on the issue:
https://github.com/apache/curator/pull/224
@Randgalt Thanks for the link i was not aware of the
https://cwiki.apache.org/confluence/display/CURATOR/TN13 ,
This would help us to leverage JDK 7 and there are few optimizations on
the ImmutableCollection https://github.com/google/guava/wiki/Release22
and when the curator moves to JDK 8 this might be handy
The intent is that the Android version always be a strict subset of what's
available in the main/Java 8 version, so anything compiled against version N of
the Android version will work when run against the Java 8 version.
For the medium-term future, Guava users who need to target JDK 7 can use
the Android flavor, which has no Android-specific dependencies. At some point
in the future, when Android diverges sufficiently from JDK 7, Guava may stop
providing a JDK 7-compatible flavor, at which time those users will have to
stay with the latest prior version
> Update to latest Guava dependecies
> ----------------------------------
>
> Key: CURATOR-417
> URL: https://issues.apache.org/jira/browse/CURATOR-417
> Project: Apache Curator
> Issue Type: Improvement
> Components: Client, General, Recipes, Tests
> Affects Versions: 3.3.0, 2.12.0
> Reporter: Ajay
> Priority: Minor
>
> guava dependency version update from 16 to 22-android
> Moving to 22-android as curator still builds from jdk 1.7
> From the Google Guava Docs ,
> If you need support for JDK 1.7 or Android, use the Android flavor. You can
> find the Android Guava source in the android directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
