accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-905) Switch to Java 1.7
Date Thu, 23 May 2013 03:53:20 GMT


Christopher Tubbs commented on ACCUMULO-905:

Update: The last security patch for Oracle JDK was 2013-04-16 (1.6.0_45). And, it looks like
OpenJDK hasn't had a tag for 1.6 in about 8 months. OpenJDK was dropped from Fedora in version
16 (currently Fedora is 18, nearing 19, on ~6 month release cycles). I'm not sure what OpenJDK
1.6 support looks like in the next major RHEL/CentOS/Ubuntu releases, but I know that OpenJDK
1.7 has been supported since RHEL/CentOS 6.3 (~June 2012).

I think the Accumulo 1.5 line will be stable enough to sustain users slow to adopt a newer
version of Java for the foreseeable future. I don't think we need to hold back use of newer
features for this any longer, personally. However, Keith is right... we should call a vote
on the dev list.
> 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