spring-projects / spring-projects/spring-security
SEC-2110: deprecation warnings in STS when using Spring Security 3.1.3 and Spring 3.2.0.
Open
Nobody has claimed this yet.
type: enhancement
type: jira
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Michael Isvy (Migrated from SEC-2110) said:
I can see warnings such as the following:
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 reproducing the STS setup with Spring Security 3.1.3 and Spring 3.2.0, then capture the deprecation warnings reported by the issue. Trace each warning to the STS area that emits it and verify the warnings are resolved without changing the intended security behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100