ksp-codegen: Spring/JPA barfs on accessing private fields

[mkoertgen]

Important Notice

Thank you for opening an issue! Please note that, as outlined in the README, I currently only work on feature requests or bug fixes when sponsored. Balancing this project with professional and personal priorities means I have a very limited amount of effort I can divert to this project.

You must put in the work to address this issue, or it won't be addressed.

• I am willing to put in the work and submit a PR to resolve this issue.

Describe the bug
The ksp-plugin is missing the option "entityAccessors" like the kapt-plugin does, so that the generated QClasses contain "public val". When booting up a spring application, the JPAAnnotationProcessor throws on accessing private final fields.

To Reproduce
Steps to reproduce the behavior:

1. Have a minimal spring/jpa application
2. Add ksp-plugin
3. Try using the Qclasses for any Entity
4. See error

Expected behavior
...

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[github-actions]

This issue has been automatically marked as stale due to inactivity. If no further action is taken, it will be closed in 7 days.

[velo]

What the example application is missing that it doesn't get this issue?

[mkoertgen]

The example app "jpa-spring" uses java & maven (so no ksp integration).

The example app "kotlin-jpa" does not use spring-jpa auto enhancement for repositories. It lacks repositories altogether.

[mkoertgen]

Well, in the meantime we switched to kapt. However, when getting some spare time I will probably get back to this.

[velo]

What about https://github.com/OpenFeign/querydsl/tree/master/querydsl-examples/querydsl-example-ksp-codegen ?

[mkoertgen]

That's what I originally used as a blueprint. When using with spring-jpa you will get the mentioned error.
When posting the original issue I missed the opportunity to add a screenshot.

[github-actions]

This issue has been automatically marked as stale due to inactivity. If no further action is taken, it will be closed in 7 days.

[github-actions]

This issue has been automatically closed due to prolonged inactivity.