[
https://issues.apache.org/jira/browse/CRUNCH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418060#comment-13418060
]
Matthias Friedrich commented on CRUNCH-16:
------------------------------------------
@Rahul: I can think of four basic options here:
1. Drop support for CDH-3 (CDH-4 ships jackson 1.8.8)
2. Drop support for jackson-smile until CDH-3 isn't supported anymore
3. Ship recent versions of jackson-* and ask CDH-3 users to set
HADOOP_USER_CLASSPATH_FIRST
4. Try if a version of jackson-smile works with the jackson-core/mapper-1.5.2
I like none of them. Option 1 may work because people who are conservative
enough to still run CDH-3 (like us) probably won't use something as young as
Crunch. Option 3 is one more way for users to shoot themselves in the foot.
Option 4 doesn't work because the libraries are really incompatible (I tried
several using our PageRankIT test case).
To be honest, I prefer option 2. People who really need smile can write those
50 LoC themselves, add the dependency, and set HADOOP_USER_CLASSPATH_FIRST.
Any ideas? Am I missing something?
> Fix dependency versions
> -----------------------
>
> Key: CRUNCH-16
> URL: https://issues.apache.org/jira/browse/CRUNCH-16
> Project: Crunch
> Issue Type: Task
> Reporter: Matthias Friedrich
> Priority: Critical
> Labels: maven
>
> 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
