You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/08/07 22:06:47 UTC

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

     [ https://issues.apache.org/jira/browse/JCLOUDS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Gaul updated JCLOUDS-652:
--------------------------------
    Fix Version/s:     (was: 1.8.2)

> 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: Adrian Cole
>
> 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)