Unable to use kapt to generate querybean in Maven
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 267
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 5
Description
Expected behavior
Generate query classes starting with Q for all @Entity and compile without errors
Actual behavior
The query class starting with Q (kotlin version) is successfully generated, and an EbeanEntityRegister.java is also generated, which will cause "cannot find Symbol" to appear during compilation
Steps to reproduce
I created a minimal example to reproduce this error, it is located here:
https://github.com/cruldra/ebean-maven-kapt-querybean-example
Contributor guide
No contributing guide indexed for this repository
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 running the minimal reproduction in cruldra/ebean-maven-kapt-querybean-example and inspect the generated Kotlin Q query class and EbeanEntityRegister.java. Reproduce the Maven compilation failure, then trace how kapt-generated sources are registered; done means @Entity query classes generate and the project compiles without the reported cannot-find-symbol error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- build-system, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100