[FOLIO-1589] Replace Oracle JDK 8 by January 2019 Created: 22/Oct/18 Updated: 19/Aug/19 Resolved: 18/Jan/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Julian Ladisch | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | back-end, core, devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Development Team: | Core: Platform | ||||||||||||
| Description |
|
FOLIO uses Oracle JDK 8: https://github.com/search?p=4&q=org%3Afolio-org+openjdk&type=Code In "Java Is Still Free" the Java Champions collected the commerical use details at https://itnext.io/java-is-still-free-c02aef8c9e04 , these are the key points: There are no longer free Oracle JDK 8 updates for commercial use after January 2019. Oracle offers a paid support plan. I WANT $FREE AND FREE (AS IN USE) JAVA SE 8, WHAT DO I CHOOSE?
I WANT $FREE AND FREE (AS IN USE) JAVA SE 11+, WHAT DO I CHOOSE?
|
| Comments |
| Comment by Julian Ladisch [ 29/Oct/18 ] |
|
Roadmap timelines: |
| Comment by John Malconian [ 29/Oct/18 ] |
|
Julian Ladisch I'm a bit confused by this, but maybe I'm overlooking a detail. Hoping you can clarify. I WANT $FREE AND FREE (AS IN USE) JAVA SE 8, WHAT DO I CHOOSE? If you want updates of Java SE 8 after January 2019, use an OpenJDK binary distribution from an OpenJDK provider, i.e. Linux distros, AdoptOpenJDK, Azul, IBM, Red Hat, and others. ^^^This is what we currently do if I'm not mistaken. The OpenJDK distribution contained in FOLIO Docker images is from the Debian distribution. I'm also curious how long we plan to develop on and support Java 8. Shouldn't we be exploring the possibility of using a more current version of Java or are restricted to Java 8 somehow? |
| Comment by Julian Ladisch [ 29/Oct/18 ] |
|
| Comment by John Malconian [ 30/Oct/18 ] |
|
ok, so this is mostly a documentation issue then. |
| Comment by Julian Ladisch [ 18/Jan/19 ] |
|
All documents have been updated (or explicitly say that they are deprecated). |