spring-projects / spring-projects/spring-security
Consider removing underused modules and APIs
Open
Nobody has claimed this yet.
theme: partner-use-cases
type: breaks-passivity
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
We should consider removing underused modules and APIs in Spring Security 7.0 to help reduce the maintenance and support overhead.
Modules
spring-security-aclspring-security-casspring-security-taglibs
APIs
TokenService
Related gh-13266
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
Review the listed modules—spring-security-acl, spring-security-cas, and spring-security-taglibs—and the TokenService API, then read related issue gh-13266. Determine the required scope and migration or compatibility considerations before any change is attempted. Done would require an agreed removal plan and defined acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100