[
https://issues.apache.org/jira/browse/GIRAPH-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902187#comment-13902187
]
Armando Miraglia commented on GIRAPH-847:
-----------------------------------------
Aha, this is something I can undrestand. However would that be a problem to
keep it retro compatbile or have a tag or a parallel branch which supports
java6? This is mainly to keep it available for more people. I mean, compiling
the same code with java7, apart from using specifics derived from java7, does
not already provide better performance? Another story is about the specific
features of java7. About that, my suggestions above are just options. I believe
there are better ways to do so :) (possibily avoid munged! :D)
> 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)
