playframework / playframework/play-json
Upgrade to Jackson 3
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 375
- Forks
- 140
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 28
Description
As per the title.
There's definitely no urgency in doing it but it'll be good to help the ecosystem move forward.
Jackson 2.x and 3.x can co-exist, so I don't think there's a reason for play-json to wait. Users will still be able to use other libraries relying on Jackson 2.x.
Maybe this is something we can include in the next minor release?
I'll be happy to work on a PR for this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Jackson 3 migration notes and then inspect play-json's dependency declarations and compatibility coverage. Done means Jackson 3 is supported without preventing coexistence with Jackson 2.x, with the project's existing checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100