incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Friedrich (JIRA)" <>
Subject [jira] [Updated] (CRUNCH-16) Fix dependency versions
Date Thu, 16 Aug 2012 20:57:38 GMT


Matthias Friedrich updated CRUNCH-16:

    Attachment: 0001-CRUNCH-16-Fix-dependency-versions.patch

Dependencies for crunch core on Hadoop 1 are OK now. HBase on Hadoop 1 still has conflicts
with Jersey, but I hope the client doesn't need it. There's nothing we can do about it anyway.
As far as I'm concerned, the hadoop-1 build profile is done.

The conflict between Hadoop 2's avro-1.5.3 and our 1.7.0 is currently unfixed. I'm not sure
what to do about this: Downgrade avro, ignore the problem, or move avro to a separate maven
module (which doesn't really solve the problem either). Ideas anyone?
> Fix dependency versions
> -----------------------
>                 Key: CRUNCH-16
>                 URL:
>             Project: Crunch
>          Issue Type: Task
>            Reporter: Matthias Friedrich
>            Assignee: Matthias Friedrich
>            Priority: Critical
>              Labels: maven
>         Attachments: 0001-CRUNCH-16-Fix-dependency-versions.patch
> Right now, the compile time classpath doesn't exactly match the runtime classpath. For
example, Hadoop CDH3u4 comes with slf4j-api-1.4.3 while Crunch references slf4j-api-1.6.3.
This could result in NoSuchMethodError and other nasty problems.
> We have to make sure that version numbers match (check "mvn dependency:tree") and that
we don't ship artifacts that are already present on the runtime classpath. If our dependencies
introduce incompatible transitive dependencies, we might have to downgrade them.
> Note: Maven's dependency resolution is order-dependent, see

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message