[
https://issues.apache.org/jira/browse/GIRAPH-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849056#comment-13849056
]
Claudio Martella commented on GIRAPH-798:
-----------------------------------------
Avery,
this is not the point. If issues are blocking our possibility to move to Java
7, those have to be fixed *BEFORE* we commit a half-backed patch, that is
forcing *MANY* users, including me, to revert the commit to before your
patches. This act, performed by many, is a proof of a bad decision. The current
trunk is in practice broken, if not for few.
Yes, we do need to get rid of munge. I did propose you guys to supervise a
third GSoC proposal that I would write, but nobody responded.
> Upgrade Giraph to Java7 and fix all dependencies
> ------------------------------------------------
>
> Key: GIRAPH-798
> URL: https://issues.apache.org/jira/browse/GIRAPH-798
> Project: Giraph
> Issue Type: Improvement
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-YARN-COMPILE.patch, GIRAPH-ZOOKEEPER34.patch
>
>
> We need to upgrade to Java 7, Java 6 is no longer supported and Java 7
> provides a lot of great new features.
> Additionally, we have a mess of dependencies.
> Incompatible versions, unspecified dependencies, and duplicate classes. We
> will add checks for all of them.
> For now, full checks are provided for the profiles
> hadoop_0.20.203
> hadoop_1.0
> hadoop_facebook
> Also, the hcatalog module is not fully fixed and excluded from the checking.
> We can fix this in the future.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
