[jira] [Commented] (JCLOUDS-652) Transition to Java 7

["Adrian Cole (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167027#comment-14167027 ] 

Adrian Cole commented on JCLOUDS-652:
-------------------------------------

try-with-resources would be used so seldomly in our mainline code I don't see any value requiring users to have a minimum SDK which would very likely require us to maintain a long-term branch. If there's something about http-client, we should detail that, and how we can't work around it now, and why this is important enough to force a long-term branch.

> Transition to Java 7
> --------------------
>
>                 Key: JCLOUDS-652
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-652
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 2.0.0
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>             Fix For: 2.0.0
>
>
> Moving to Java 7 allows jclouds to use more language and library features such as try-with-resources and HTTP client improvements.  We previously discussed dropping Java 6 support for jclouds 2.0 on the user mailing list:
> http://mail-archives.apache.org/mod_mbox/jclouds-user/201405.mbox/%3C20140528185718.GC1036@sherlock%3E
> We need to unhook the Java 6 CloudBees builders before committing the Maven compile requirement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)