spring-projects / spring-projects/spring-security
Document Jackson 3 Migration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Document how the switch to Jackson 3 is a breaking change. For example, users with custom Security classes that are mapped with Jackson 2 may need to update to Jackson 3. We should also document how users can explicitly choose to use Spring Security with Jackson 2 for classes like JdbcOAuth2AuthorizationService
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 reviewing the existing documentation for Jackson 2 and the JdbcOAuth2AuthorizationService entry point. Document the breaking changes for custom Security classes mapped with Jackson 2, and explain how users can explicitly keep using Spring Security with Jackson 2. Done means both migration guidance and the Jackson 2 choice are clearly covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100