jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-652) Transition to Java 7
Date Sat, 09 Aug 2014 07:30:12 GMT

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

ASF subversion and git services commented on JCLOUDS-652:
---------------------------------------------------------

Commit 5e8bd02c93c7ebacb573342e77ef7ca4b02c4ffb in jclouds's branch refs/heads/master from
[~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=5e8bd02 ]

JCLOUDS-652: Require JDK 7

Moving to Java 7 allows jclouds to use more language and library
features such as try-with-resources and HTTP client improvements.


> 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
>
> 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.2#6252)

Mime
View raw message