[ 
https://issues.apache.org/jira/browse/CASSANDRA-16851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tatu Saloranta updated CASSANDRA-16851:
---------------------------------------
    Description: 
Given that Jackson 2.9 support has ended, it would be good to move at least to 
the next minor version (2.10, patch 2.10.5) or later – latest stable being 
2.12.4.
 I can test to see if anything breaks, but looking at existing Jackson usage 
there shouldn't be many issues.

Assuming upgrade is acceptable there's the question of which branches to apply 
it to; I will first test it against 4.0.

  was:
Given that Jackson 2.9 support has ended, it would be good to move at least to 
the next minor version (2.10, patch 2.10.5).
I can test to see if anything breaks, but looking at existing Jackson usage 
there shouldn't be many issues.

Assuming upgrade is acceptable there's the question of which branches to apply 
it to; I will first test it against 4.0.


> Update from Jackson 2.9 to 2.12
> -------------------------------
>
>                 Key: CASSANDRA-16851
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16851
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Dependencies
>            Reporter: Tatu Saloranta
>            Assignee: Tatu Saloranta
>            Priority: Normal
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Given that Jackson 2.9 support has ended, it would be good to move at least 
> to the next minor version (2.10, patch 2.10.5) or later – latest stable being 
> 2.12.4.
>  I can test to see if anything breaks, but looking at existing Jackson usage 
> there shouldn't be many issues.
> Assuming upgrade is acceptable there's the question of which branches to 
> apply it to; I will first test it against 4.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to