On 04/06/18 15:24, Elana Hashman wrote: > Hi Emilio, > > Why was this bug filed as serious? Leiningen has a direct dependency on > Java 8 and upstream has not yet been updated to use a newer version of > Java, as the public Java 11 builds aren't really available yet. I had to > pin the build to Java 8 as it does not work properly with Java 9+ yet. > Java 11 won't even be released until September I think? > > I was not under the impression that Java 8 would be removed from buster, > so I don't see this bug as release critical. While it might not be > officially supported by upstream, RedHat should still be releasing > security patches.
OpenJDK 8 will be EOL sometime in 2020 (Red Hat will drop support for it in October 2020). With a buster release in mid 2019, that would only be a little over one year into buster's release. With 3 years of main support, that won't be enough. Thus the OpenJDK maintainers aim to switch to Java 11 for buster (default-jdk already points to 10, and will be switched to 11 once it's released in September) [1]. Also note that pre-releases of 11 are available in sid and testing. I filed this bug as serious so that you are aware that buster will release without openjdk-8 and can prepare for that. Perhaps upstream could start the porting work already using the Java 11 pre-releases, or porting to Java 10 now and to 11 once it's out (a 10 -> 11 port would probably be easier than a 8 -> 11 one). Let me know if you have any questions or concerns. Cheers, Emilio [1] https://lists.debian.org/debian-java/2018/04/msg00038.html
