-
Notifications
You must be signed in to change notification settings - Fork 591
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
gRPC generated java references javax.annotation.Generated which is not in Jakarta #23922
Comments
The actions/questions here are: 2: I would think we would want to be careful NOT to ship javax.annotations.Generated if |
https://search.maven.org/artifact/javax.annotation/javax.annotation-api/1.3.2/jar |
The grpc guide has been changed to pull in the javax package without doing so via tomcat, so this is no longer an urgent design issue. I will see if I can include the same include they use ONLY if we are in Jakarta mode as part of the base feature. |
I put this in parked for now - please let me know if status changes... |
There are two follow on actions for this: |
gRPC protobuf tools generate Java that has annotations that are NOT retained at runtime of
javax.annotation.Generated
Such java will not compile with Liberty in Jakarta 9/10 as that package is not present.
There are 2 possible solutions currently:
1 - Use the Eclipse transformer (The Liberty gRPC 1.0 guide stopped short of including this for simplicity's sake.)
2 - Add in a dependency, for example the gRPC read.me recommends:
grpc/grpc-java#9179 (comment)
(The Liberty gRPC guide ++ looks like it wants to use that route:
OpenLiberty/guide-grpc-intro#43 )
to the compile dependencies IFF gRPC and Jakarta EE9/10... etc is the mode?
After all tomcat are bundling it without 'owning' the javax.annotation package so we should
be able do the same in a way that avoids it being on the compile classpath if NOT Jakarta?
The text was updated successfully, but these errors were encountered: