spring-projects / spring-projects/spring-boot
Disable annotation processing in AOT compilation step
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
By default, the compiler attempts to discover annotation processors from the classpath. This can have side effect on code that is generated ahead of time.
Adding -proc:none in the Maven and Gradle integration could be on way of making sure these don't run.
See also https://github.com/spring-projects/spring-framework/issues/30824 which now annotates every generated class which should trigger a warning if AP is active and no processor claimed it (which is likely to happen).
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 tracing the Maven and Gradle integration entry points for the AOT compilation step and determine where annotation processors are discovered from the classpath. Done means both integrations disable annotation processing during AOT compilation and generated classes no longer trigger warnings from unclaimed processors.
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
- 35/100