You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently operate on Java 8 (issue #1463) and have been prevented in upgrading because of hazelcast needing Java 10 and beyond (issue #1313). Metacat should be operable on supported JVM versions, particularly OpenJDK 11 which is the most recent LTS version. It should be supported through 2026 by AdoptOpenJDK. Java 15 is the current release, which will only be supported until Java 16 comes out in March 2021. See https://en.wikipedia.org/wiki/Java_version_history for a summary.
For us, I think this means we should 1) compile using source compatibility against the most recent LTS version (11 at this time), and 2) ensure our build and tests pass and that we can run under the most recent version (currently 15) at the time of each metacat release.
On the longer time front, I worry about the availability of open java support, and we should be moving towards a more modular infrastructure, and the extent possible refactor subystems like indexing that can stand alone and be gradually migrated to other languages if it makes sense.
To close this issue:
Change the metacat build to use source compatibility with the most recent LTS (Java 11), and build releases with that version
Test that the release works with the most recent java version (currently Java 15)
The text was updated successfully, but these errors were encountered:
With the removal of Hazelcast, we should now be able to move up to modern Java LTS releases. I suggest we should require Java 17 in the 3.0.0 release, so I am retargeting to that milestone and retargeting the issue.
mbjones
changed the title
support java 11 source compatibility and current JVM releases
support java 17 source compatibility and current JVM releases
Nov 3, 2023
We currently operate on Java 8 (issue #1463) and have been prevented in upgrading because of hazelcast needing Java 10 and beyond (issue #1313). Metacat should be operable on supported JVM versions, particularly OpenJDK 11 which is the most recent LTS version. It should be supported through 2026 by AdoptOpenJDK. Java 15 is the current release, which will only be supported until Java 16 comes out in March 2021. See https://en.wikipedia.org/wiki/Java_version_history for a summary.
For us, I think this means we should 1) compile using source compatibility against the most recent LTS version (11 at this time), and 2) ensure our build and tests pass and that we can run under the most recent version (currently 15) at the time of each metacat release.
On the longer time front, I worry about the availability of open java support, and we should be moving towards a more modular infrastructure, and the extent possible refactor subystems like indexing that can stand alone and be gradually migrated to other languages if it makes sense.
To close this issue:
The text was updated successfully, but these errors were encountered: