spring-projects / spring-projects/spring-boot
Allow ConfigurationProcessor to work with Kotlin Symbol Processor
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
The problem:
Currently, ConfigurationProcessor is backed by Annotation Processing. In Kotlin annotation processors can be used thanks to KAPT. Sadly KAPT does not work with JDK 16+ ( https://youtrack.jetbrains.com/issue/KT-45545 ). For Kotlin there are other processors like KSP ( https://github.com/google/ksp ), yet they do not rely on Java Annotation processing.
Proposed solution:
Provide an abstraction layer on ConfigurationMetadataAnnotationProcessor that will allow plugging in other processors.
Additionally provide an adapter for KSP.
@sdeleuze
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 ConfigurationMetadataAnnotationProcessor and compare its annotation-processing assumptions with the linked KSP documentation and KAPT limitation. Done means an abstraction allows alternate processors and Spring Boot provides a working KSP adapter, with processor behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin, spring-boot
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100