[
https://issues.apache.org/jira/browse/GIRAPH-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591384#comment-13591384
]
Hudson commented on GIRAPH-545:
-------------------------------
Integrated in Giraph-trunk-Commit #760 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/760/])
GIRAPH-545: Improve Facebook Hadoop dependency (nitay) (Revision
831e9eaada9dd5ce0a6b3e30150e707a1733110c)
Result = FAILURE
nitay :
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=831e9eaada9dd5ce0a6b3e30150e707a1733110c
Files :
* lib/facebook-hadoop-0.20-test.jar
* giraph-hbase/pom.xml
* giraph-accumulo/pom.xml
* giraph-hcatalog/pom.xml
* lib/facebook-hadoop-0.20-core.jar
* pom.xml
* CHANGELOG
> Improve Facebook Hadoop dependency
> ----------------------------------
>
> Key: GIRAPH-545
> URL: https://issues.apache.org/jira/browse/GIRAPH-545
> Project: Giraph
> Issue Type: Bug
> Reporter: Nitay Joffe
> Assignee: Nitay Joffe
> Attachments: GIRAPH-545.patch
>
>
> The Facebook Hadoop dependency uses a local path (systemPath in maven) which
> is bad for many reasons. See e.g.
> http://docs.codehaus.org/display/MAVENUSER/Dependency+Scopes (the part about
> system scope). Amongst the problems are:
> - We package the jar ourselves in our lib/ folder
> - Anyone depending on Giraph needs to download jars themselves and put them
> in right place, but we don't supply the jars.
> - There is no javadoc or sources jar which comes with most open source maven
> projects and is really handy
> So I went ahead and created a package from Facebook's code on Github and
> published the jar to maven central. This diff updates our code to use that,
> which fixes all of the problems mentioned above.
--
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: http://www.atlassian.com/software/jira
