-
Notifications
You must be signed in to change notification settings - Fork 42
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
allow the jakarta version of @Generated instead of the javax one. #194
Comments
Zegveld
added a commit
to rigd-loxia/assertj-assertions-generator
that referenced
this issue
Jan 14, 2022
…choose between javax.annotation.Generated and jakarta.annotation.Generated. Or if you really do not want any no annotation (not recommended).
Zegveld
added a commit
to rigd-loxia/assertj-assertions-generator
that referenced
this issue
Jan 26, 2022
…can now choose between javax.annotation.Generated and jakarta.annotation.Generated. Or if you really do not want any no annotation (not recommended)." This reverts commit 3d0a7eb.
Zegveld
added a commit
to rigd-loxia/assertj-assertions-generator
that referenced
this issue
Jan 26, 2022
Zegveld
added a commit
to rigd-loxia/assertj-assertions-generator
that referenced
this issue
Jan 26, 2022
+1 |
@joel-costigliola , any reason why the jakarta support doesn't get merged? |
just lack of time, the generator is currently in a limbo state because of that ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
all javax modules are being replaced with jakarta, this includes
@javax.annotation.Generated
. This is replaced by@jakarta.annotation.Generated
, allow users to choose which annotation they want on the generated classes.(I'm also creating a PR for this.)
The text was updated successfully, but these errors were encountered: