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

Akira Ajisaka commented on HADOOP-13332:
----------------------------------------

Filed HADOOP-13842 and attached a patch there.
Now jersey-json, avro, hbase-server, and hbase-client depend on jackson 1.9.x. 
We cannot remove the setting in hadoop-project pom.xml.
{noformat:title=mvn dependency:tree}
[INFO] +- com.sun.jersey:jersey-json:jar:1.19:compile
[INFO] |  +- org.codehaus.jettison:jettison:jar:1.1:compile
[INFO] |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile
[INFO] |  |  \- javax.xml.bind:jaxb-api:jar:2.2.11:compile (version managed 
from 2.2.2)
[INFO] |  +- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile (version 
managed from 1.9.2)
[INFO] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile 
(version managed from 1.9.2)
[INFO] |  +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.13:compile (version 
managed from 1.9.2)
[INFO] |  \- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile (version 
managed from 1.9.2)
{noformat}

> Remove jackson 1.9.13 and switch all jackson code to 2.x code line
> ------------------------------------------------------------------
>
>                 Key: HADOOP-13332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13332
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.8.0
>            Reporter: PJ Fanning
>            Assignee: Akira Ajisaka
>         Attachments: HADOOP-13332.00.patch, HADOOP-13332.01.patch, 
> HADOOP-13332.02.patch, HADOOP-13332.03.patch
>
>
> This jackson 1.9 code line is no longer maintained. Upgrade
> Most changes from jackson 1.9 to 2.x just involve changing the package name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to