[
https://issues.apache.org/jira/browse/HADOOP-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214931#comment-13214931
]
Colin Patrick McCabe commented on HADOOP-8104:
----------------------------------------------
Hi Alejandro,
I have posted the complete dependency tree in case you want to look at it. You
can get the same output yourself by running {{mvn dependency:tree}}. The
project that is pulling in jackson 1.7.1 appears to be hadoop-common. The
reason why it is pulled in is because Jersey 1.8 explicitly depends on jackson
1.7.1, and not a later version. The mixed versions are creating runtime
exceptions.
There is a StackOverflow question about this exact problem at
http://stackoverflow.com/questions/6537287/jersey-and-jackson-maven-dependency-issues
> Inconsistent Jackson versions
> -----------------------------
>
> Key: HADOOP-8104
> URL: https://issues.apache.org/jira/browse/HADOOP-8104
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HADOOP-8104.patch, dependency-tree-old.txt
>
>
> This is a maven build issue.
> Jersey 1.8 is pulling in version 1.7.1 of Jackson. Meanwhile, we are
> manually specifying that we want version 1.8 of Jackson in the POM files.
> This causes a conflict where Jackson produces unexpected results when
> serializing Map objects.
> How to reproduce: try this code:
> {quote}
> ObjectMapper mapper = new ObjectMapper();
> Map<String, Object> m = new HashMap<String, Object>();
> mapper.writeValue(new File("foo"), m);
> {quote}
> You will get an exception:
> {quote}
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.codehaus.jackson.type.JavaType.isMapLikeType()Z
> at
> org.codehaus.jackson.map.ser.BasicSerializerFactory.buildContainerSerializer(BasicSerializerFactory.java:396)
> at
> org.codehaus.jackson.map.ser.BeanSerializerFactory.createSerializer(BeanSerializerFactory.java:267)
> {quote}
> Basically the inconsistent versions of various Jackson components are causing
> this NoSuchMethod error.
> As far as I know, this only occurs when serializing maps-- that's why it
> hasn't been found and fixed yet.
--
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
