[bisq-network/bisq] Java 10 is EOL, move to Java 11 (#1787)
notifications at github.com
Thu May 7 15:04:56 UTC 2020
> The primary item blocking us is there is no javapackager in JDK11. However, progress is being made on its replacement https://jdk.java.net/jpackage/ which is based on JDK 13. The next LTS release (JDK 17?) is still a few years away and no idea if this will be ported to the current LTS, JDK11. So unless we find an alternative solution, we may be stuck on JDK10 for a while.
If I understand [this](https://openjdk.java.net/jeps/343) correctly, `jpackager` is available in Java 14, and [Java 14 is already GA](https://jdk.java.net/14/).
>From what I see, getting the latest `jpackager` could directly solve a bunch of issues, like #3373 #3402 and #4196. Also, an upgrade of Java would make #4242 possible, which seems to address (or at least improve) a lot of JavaFX-related memory and performance issues.
Would it then make sense to upgrade to Java 14?
Or are there other blockers preventing this / other reasons not to?
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github