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 15:53:20 GMT


Christopher Tubbs commented on ACCUMULO-905:

{quote}Are there any statistics about how many groups are using 1.6 versus 1.7?{quote}

I did some Googling, but wasn't able to find anything useful.

{quote}What is the government using?{quote}

I suspect "the government" is using many different versions, depending on which government,
and which agency, and maybe even which employee, you are referring to. I think it's probably
more useful to discuss in terms of what is best supported by modern operating systems that
are likely to be used in an enterprise cloud architecture. To get a sense of that, it might
be best to sample the operating systems used on a public cloud, like on EC2, if they publish
those data.
> 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