-
Notifications
You must be signed in to change notification settings - Fork 869
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
Add support for Jakarta annotations + Jakarta persistence (in jakarta.* packages) #2612
Comments
Seems that a solution for #2657 would actually solve the issue w.r.t. I'm not really interested in supporting the |
EclipseLink 3.0 is out since Dec 8th, 2020 which implements jakarta-persistence-api 3.0 |
@jwgmeligmeyling Please reopen this feature request. There will be no way around supporting jakarta.persistence in the future. |
Issue was automatically closed when I fixed the other issue the TS asked for: Java 9+ support. I am working on full Jakarta EE API support in #2726 |
[#2612] Support Jakarta EE through Eclipse Transformer
Can someone shed a light how this can be solved if you are still using
|
OK, I found it myself hidden in a different issue:
Would be nice, if you could update your documentation. See e.g. http://querydsl.com/static/querydsl/latest/reference/html/ch02.html#d0e147 - IMHO you should add the classifier in RED and explain below to remove it for |
Currently, when building a project with QueryDSL-APT 4.3.1 and jakarta.annotation-api 2.0.0-RC1, no Q-classes are generated (with an error message like "java.lang.NoClassDefFoundError: javax/annotation/Generated"). It still works with jakarta.annotation-api 1.3.5.
With Jakarta EE, many types in the javax.* package are moved to the jakarta.* packages.
This includes the Annotation types in javax.annotations, and it looks like javax.annotation.Generated is now jakarta.annotation.Generated.
The same happens when using jakarta.persistence-api 3.0.0-RC2 (instead of 2.2.3), here the problem is javax.persistence.Entity → jakarta.persistence.Entity.
The text was updated successfully, but these errors were encountered: