Create rules for bean handling annotations
- Dominant language
- Java
- Stars
- 6
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
According to the [migration guide](https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-6.0-Release-Notes#core-container):
> The JSR-330 based @Inject annotation is to be found in jakarta.inject now. The corresponding JSR-250 based annotations @PostConstruct and @PreDestroy are to be found in jakarta.annotation. For the time being, Spring keeps detecting their javax equivalents as well, covering common use in pre-compiled binaries.
Investigate and create rules if necessary.
In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.
Contributor guide
Research direction
Start with the linked Spring Framework 6.0 migration guide and inspect how this repository represents rules for annotation changes. Determine whether rules are needed for @Inject, @PostConstruct, @PreDestroy and their Jakarta equivalents, then provide verbose rule descriptions, messages, and useful Markdown examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100