[
https://issues.apache.org/jira/browse/JCLOUDS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184195#comment-14184195
]
ASF subversion and git services commented on JCLOUDS-652:
---------------------------------------------------------
Commit 8b6081bb943ea170f7462839074f2031b6feb73b in jclouds's branch
refs/heads/1.8.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8b6081b ]
JCLOUDS-652 Pin filesystem api to Java 7+.
> 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
> 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)
