avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Honton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1126) Upgrade to Jackson 2+
Date Mon, 11 Jul 2016 00:15:11 GMT

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

Charles Honton commented on AVRO-1126:
--------------------------------------

Is this still targeted against 1.8? Or 1.9? If 1.9, can someone with commit rights create
branch-1.9?

> Upgrade to Jackson 2+
> ---------------------
>
>                 Key: AVRO-1126
>                 URL: https://issues.apache.org/jira/browse/AVRO-1126
>             Project: Avro
>          Issue Type: Task
>          Components: java
>            Reporter: James Tyrrell
>            Priority: Critical
>             Fix For: 1.9.0
>
>
> Quite annoyingly with Jackson 2+ the base package name has changed from org.codehaus.jackson
to com.fasterxml.jackson so in addition to changing the dependencies from:
> {code:xml} 
> <dependency>
>     <groupId>org.codehaus.jackson</groupId>
>     <artifactId>jackson-core-asl</artifactId>
>     <version>${jackson.version}</version>
> </dependency>
> <dependency>
>     <groupId>org.codehaus.jackson</groupId>
>     <artifactId>jackson-mapper-asl</artifactId>
>     <version>${jackson.version}</version>
> </dependency>
> {code} 
> to:
> {code:xml} 
> <dependency>
>     <groupId>com.fasterxml.jackson.core</groupId>
>     <artifactId>jackson-core</artifactId>
>     <version>${jackson.version}</version>
> </dependency>
> <dependency>
>     <groupId>com.fasterxml.jackson.core</groupId>
>     <artifactId>jackson-databind</artifactId>
>     <version>${jackson.version}</version>
> </dependency>
> {code} 
> the base package in the code needs to be updated. More info can be found [here|http://wiki.fasterxml.com/JacksonUpgradeFrom19To20],
I am happy to do the work just let me know what is preferable i.e. should I just attach a
patch to this issue?



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

Mime
View raw message