[jira] [Comment Edited] (JENA-842) Elephas IO library does not build

["Andy Seaborne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264690#comment-14264690 ] 

Andy Seaborne edited comment on JENA-842 at 1/5/15 3:41 PM:
------------------------------------------------------------

Breakign the Elphas build is not good - do reverse the jena-parent management of Guava.  (jena-csv needs  version set but otherwise it's not actually used yet; though I was hoing to use it for the concurrent cache for TDB where it's been shown to make things better.)

How about the suggestion in:

http://mail-archives.apache.org/mod_mbox/jena-dev/201501.mbox/%3C54A6F60F.1050106%40apache.org%3E

? 

That's is, limit Guava to specific modules (jena-dtb, jena-csv).

Plan B : Shade the relevant cache bits 
Plan C:  Take a code copy of the relevant cache bits and repackage.



was (Author: andy.seaborne):
How about the suggestion in:

http://mail-archives.apache.org/mod_mbox/jena-dev/201501.mbox/%3C54A6F60F.1050106%40apache.org%3E

? 

That's is, limit Guava to specific modules (jena-dtb, jena-csv).

Plan B : Shade the relevant cache bits 
Plan C:  Take a code copy of the relevant cache bits and repackage.


> 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)