[
https://issues.apache.org/jira/browse/GIRAPH-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842321#comment-13842321
]
Alexandre Fonseca commented on GIRAPH-798:
------------------------------------------
I confirm this change made it impossible to compile giraph with a hadoop_yarn
profile and hadoop version 2.2.0, resulting in the errors described in
GIRAPH-804. Reverting to the previous commit affecting the pom.xml file
[357c186584ddce07853db125c5de09ccc144e5d3|https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=commit;h=357c186584ddce07853db125c5de09ccc144e5d3]
results in clean compilation with no errors with the same settings:
mvn -Phadoop_yarn -Dhadoop.version=2.2.0 -DskipTests compile
The resulting .jars also appear to be valid as I was able to run the
SimpleShortestPaths example.
> 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
>
> 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#6144)
