incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-16) Fix dependency versions
Date Tue, 21 Aug 2012 15:02:38 GMT

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

Gabriel Reid commented on CRUNCH-16:
------------------------------------

Josh, that's almost exactly what I was talking about, but I was actually thinking of having
the CAN_COMBINE_SPECIFIC_AND_REFLECT_SCHEMAS automatically initialized (in a static initializer
block) by a kind of mini-test that would actually actually attempt to combine both in a single
schema and set the static field as a result of that test. However, I'm kind of on the fence
as to whether it's worth it adding those kinds of moving parts to satisfy a use case that
probably won't come up much. 

I'm ok with it either way, but I don't mind taking a crack at implementing that idea if you
think it's worth including it.
                
> Fix dependency versions
> -----------------------
>
>                 Key: CRUNCH-16
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-16
>             Project: Crunch
>          Issue Type: Task
>            Reporter: Matthias Friedrich
>            Assignee: Matthias Friedrich
>            Priority: Critical
>              Labels: maven
>         Attachments: 0001-CRUNCH-16-Fix-dependency-versions.patch, CRUNCH-16-avro-preparation.patch,
CRUNCH-16-avro-reflect-specific-static-init.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 http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message