giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Armando Miraglia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-847) Add back java 6 source compatibility
Date Fri, 14 Feb 2014 23:29:19 GMT

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

Armando Miraglia commented on GIRAPH-847:
-----------------------------------------

as for me, many other Giraph users are bounded by the clusters they are using. Independently
whether java6 is no longer supported, clusters used by users and managed by third parties
are still bounded to java6. Supporting it allows this users to be able to still use Giraph.
Moreover, the only additional features used currently are the possibility to "pipe" Execptions
and possibly to leave the Generic specification unspecified (see ArrayList used in Zookeeper,
if I am not wrong). Are these syntactic features so important that the compatibility cannot
be kept?

> Add back java 6 source compatibility
> ------------------------------------
>
>                 Key: GIRAPH-847
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-847
>             Project: Giraph
>          Issue Type: Wish
>          Components: build
>    Affects Versions: 1.1.0
>            Reporter: Craig Muchinsky
>            Priority: Minor
>         Attachments: GIRAPH-847.patch
>
>
> While I understand that java 7 is the default for Giraph now, I suspect there are some
folks such as myself who are stuck with java 6 for the time being. It doesn't seem like Giraph
is heavily taking advantage of java 7 features yet so it might be nice if the remainder of
the 1.x releases keep java 6 source compatibility (at least for graph-core). By my count there
are only 6 source files in giraph-core that use java 7 syntax.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message