spring-projects / spring-projects/spring-security
Fail on all deprecations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
We should fail on all deprecations (not just for removal) by adding options.compilerArgs += "-Xlint:deprecation"
An incremental way of doing this is we could have a strictcompile-warnings-error which applies compile-warnings-error but also sets options.compilerArgs += "-Xlint:deprecation". Then modules we can incrementally apply the more restrictive plugin.
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 locating the compile-warnings-error configuration and the modules that use it. Review how compilerArgs are currently set, then determine whether the incremental strictcompile-warnings-error approach is needed. Done means deprecations fail compilation consistently for the modules adopting the stricter configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100