You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Immutables (within JPA entities) and QueryDSL together
Run mvn clean generate-sources
Immutables are not generated in this step
QueryDSL (which generates the metamodel classes in the correct phase generate-sources) expects the Immutables and write error messages during the maven generate-sources phase
Note: The mvn install leads to a correct build, but error messages should be avoided
Wanted solution:
Immutable classes should be generated in the maven step "generate-sources"
This has also the advantage that even in case of compile errors the Immutables already exists and the "real error" does not hide between lots of "Immutable not found" errors.
The text was updated successfully, but these errors were encountered:
I think I ran into a similar problem typetools/checker-framework#5143
Thanks for the link.
As far as I understood it, it was about two different plugins both being executed in the maven lifecycle compile, but one of them was no longer executed.
Your solution from the link:
If you run "mvn clean generate-sources", the autogenerated classes of both plugins are "missing", aren't they?
I have now got QueryDSL to generate the classes in the compile lifecylce (annotationProcessor) only but this has other disadvantages and that is why I am not so happy with it
Steps to reproduce
Note: The mvn install leads to a correct build, but error messages should be avoided
Wanted solution:
Immutable classes should be generated in the maven step "generate-sources"
This has also the advantage that even in case of compile errors the Immutables already exists and the "real error" does not hide between lots of "Immutable not found" errors.
The text was updated successfully, but these errors were encountered: