spring-projects / spring-projects/spring-security
Consider removing XML configuration support
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
Providing both Java and XML configuration support requires higher maintenance overhead. We should consider removing XML configuration support in Spring Security 7.0, to help reduce the maintenance and support overhead.
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
The issue names no files, tests, or entry points. Review related issue gh-13266 and map the existing Java and XML configuration support before deciding whether removal is feasible; “done” is not defined beyond considering removal in Spring Security 7.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100