-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entity and Wrapper code generators in Gradle - please document #183
Milestone
Comments
hrstoyanov
changed the title
Entity and Wrapper code gemerators in Gradle - please document!
Entity and Wrapper code gemerators in Gradle - please document
Mar 25, 2024
So this seems like a small bug in the EclipseStore annotation processor. Here is how to fix it: |
fixed the erroneous annotation processor definition in PR eclipse-serializer/serializer#123 |
Thanks for the quick fix! You also may want to fix the docs, since now it should not be required (in both Maven and Gradle) to explicitly specify the processor class - the build tool should be able to figure it out by examining the jar only. |
hrstoyanov
changed the title
Entity and Wrapper code gemerators in Gradle - please document
Entity and Wrapper code generators in Gradle - please document
Apr 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please consider adding the below example code to the relevant ES documentation sections - it may save Gradle users headaches and frustrations.
A Gradle user migth attempt to add ES generators as per the Gradle docs like shown below (where all information is extracted from the codegen jar and manifest):
Unfortunately, this works for the
codegen-wrapper
, but not forcodegen-entity
, which is simply ignored by Gradle 8.6+. I filed a Gradle issue for that, and we need to see what the Gradle team says (but I suspectcodegen-entity
is ignored because it does not declare to really processes any annotations).In the meantime, here is a workaround that works fine: adding explicit
-processor
option to the javac command line to point to the processor class(es). Here is an example of enabling both ES code generators (note how the processor classes are comma-separated):The text was updated successfully, but these errors were encountered: