[
https://issues.apache.org/jira/browse/JENA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264693#comment-14264693
]
Rob Vesse commented on JENA-842:
--------------------------------
The problem isn't quite the same, Elephas doesn't need Guava at all itself but
the Hadoop runtime does have a transitive dependency on Guava. The problem is
with the use of {{<dependencyManagement>}}, as there is an entry for Guava in
{{jena-parent}} the managed version there overrides the transitively resolved
dependency from Hadoop which leads to the build error.
In the slightly longer term the Hadoop folks have a patch which would allow
them to update to the latest Guava and resolve the conflict.
> Elephas IO library does not build
> ---------------------------------
>
> Key: JENA-842
> URL: https://issues.apache.org/jira/browse/JENA-842
> Project: Apache Jena
> Issue Type: Bug
> Components: RDF Tools for Hadoop
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Fix For: Jena 2.12.2
>
>
> Currently the Elephas modules no longer build due to a bug in the upstream
> Hadoop libraries related to Guava - HADOOP-11032
> Rolling back to 752646c i.e. prior to my merging of the latest Jena master
> changes the issue does not manifest which means this likely relates to the
> introduction of Guava as a dependency into Jena since the Hadoop libraries
> were relying on a really old version of Guava. Looking at {{mvn
> dependency:tree}} this indeed appears to be the case since the managed
> dependency of Guava in the Jena parent POM overrides the transitive
> dependency from Hadoop
> A temporary workaround may be to override back to the outdated Guava in the
> elephas POM while awaiting a fix for the Hadoop issue
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
