accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-905) Switch to Java 1.7
Date Tue, 05 Feb 2013 19:18:13 GMT


Keith Turner commented on ACCUMULO-905:

For Accumulo 1.5, if you test it against Java 1.7 and find issues please open bugs.  

I agree w/ Benson dropping support for Java 1.6 is a serious decision.  We can easily produce
class files that work against Java 1.6 and Java 1.7 as long as we do not utilize new Java
1.7 features in Accumulo 1.6.   While using new Java features would be nice, would any of
these new features be necessary?  From a security standpoint, a user can use Java 1.7 without
use producing class files that only work with Java 1.7.
> Switch to Java 1.7
> ------------------
>                 Key: ACCUMULO-905
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>              Labels: java, jdk1.7
>             Fix For: 1.6.0
>         Attachments: ACCUMULO-905-1.patch
>   Original Estimate: 5m
>          Time Spent: 0.05h
>  Remaining Estimate: 2m
> As 1.7 becomes the default Java in more and more operating systems, and security-related
bugfixes and other fixes in Java itself are targeted more towards newer versions, rather than
maintaining older versions, it would be prudent to switch to using 1.7 as our target platform.
> This change would allow us to leverage some of the newer features of Java.
> This change can be established at the beginning of the development cycle for Accumulo
1.6.0, so that we can immediately begin taking advantage of the new Java features in 1.6.0
features after 1.5.0 is released.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message