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

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

Josh, about the various Avro dependencies, what do you think of just having 
some kind of static field somewhere that defines whether or not the capability 
of the ReflectDatumReader to properly handle all datum types present? This 
could then be set up in a static initializer, and then the creation of PTypes 
that combine Specific and Reflect could be disallowed at runtime (and the same 
logic would be needed to decide on whether certain unit tests should be run).

If that sounds like it's in line with what you were thinking, I can try to put 
that together later today and update the patch.
                
> 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
>
>
> 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

        

Reply via email to