incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-16) Fix dependency versions
Date Sat, 18 Aug 2012 06:42:38 GMT


Josh Wills commented on CRUNCH-16:

I'm taking a crack at a patch for what is needed to have things work as seamlessly as possible
from Avro 1.5.4 through Avro 1.7.1. My preference would be for the most recent version of
Avro that has API compatibility w/Avro 1.5.3. It's a bit of a slog, but I think I'll get it
done tomorrow.

I looked at the newest Crunch-16, and everything looks fine except for the versions on the
protobuf dependencies-- I think 2.3.1, 2.4.0a, and 2.4.1 are all getting referenced at some
> 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