Replies: 3 comments
-
It is not only ok to move to java 11+, I'd say it would make my life much easier being able to constantly move forward and not being stuck with legacy versions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Okay, so the baseline for all ph-projects will shift from Java 8 to Java 11 over the next weeks |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently ph-commons and all my other ph* libraries use Java 1.8 as the baseline, as it provides all the needed features and has nice coverage. New releases of existing, commonly used libraries, like JAXB, JAX-WS etc. enforce Java 11 as the baseline so the ph* libraries cannot be updated to the latest and greatest version.
Updating to Java 11 as the baseline of all the libraries would mean:
An update to Java 11 does not mean:
var
) will be added to the components8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions