-
Notifications
You must be signed in to change notification settings - Fork 357
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
Support JDK19 #5124
Support JDK19 #5124
Conversation
jbescos
commented
Aug 10, 2022
Signed-off-by: Jorge Bescos Gascon <jorge.bescos.gascon@oracle.com>
...c/test/java/org/glassfish/jersey/internal/config/SystemPropertiesConfigurationModelTest.java
Outdated
Show resolved
Hide resolved
org.apache.groovy:groovy-all: CQ24207 |
Signed-off-by: Jorge Bescos Gascon <jorge.bescos.gascon@oracle.com>
My JDK: java version "19.0.1"
Java(TM) SE Runtime Environment (build 19.0.1+5-12)
Java HotSpot(TM) 64-Bit Server VM (build 19.0.1+5-12, mixed mode, sharing) And the result:
Is it an odd JDK bug? |
There is no such |
@jbescos, it appears since 3.x - added a year ago by Payara guys. But when your PR is merged into the 3.x, this will become an issue :) however, this is very probably a bug in JDK not in your (or theirs) code. |
It looks adding this --enable-preview should pass. We can also wait for a final JDK19 version to try it. |
JerseyHttpClientThread has:
But the compiler for some reason thinks the Builder is |
Yes, I noticed that and it makes no sense. There is no point to fail with that because the signature of the method clearly returns We can wait for a final JDK19 release and compile with it. Is there a release date for that?. |
After a discussion with the JDK team: The issue is that
|
I see. Anyway that is for 3.x branch because in master there is no JerseyHttpClientThread class. I can create a separate PR to make that change to prevent this issue will happen once we migrate master changes to 3.x: |