spring-projects / spring-projects/spring-framework
Add shortcut to fail compilation when calling deprecated code without it being suppressed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
As a companion of CodeWarnings, it'd be nice if we could easily configure a TestCompiler to fail if the generated code calls deprecated code or exposes a deprecated type without suppressing the warning.
Enabling it for every AOT-related tests could also make sure it doesn't surface by accident.
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 reading the existing CodeWarnings support and the TestCompiler entry point, then inspect how AOT-related tests configure compilation. Define the shortcut so compilation fails for unsuppressed deprecated calls or exposed deprecated types, and verify that enabling it for AOT-related tests catches such warnings without affecting suppressed cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100