Hi, a couple of more ideas / comments
1. Use multi release jar's to be compatible with 8 and 9 - maybe changes to NetBeans custom classloaders needed? 2. Upgrade real old required source levels, which are not supported anymore beginning with Java 9 -Sven Am 18.02.2018 1:19 nachm. schrieb "Neil C Smith" <[email protected]>: On Sat, 17 Feb 2018 at 23:37 Martin Dindoffer <[email protected]> wrote: > Because after 9, there will be 10, and after 10, 11. From my experience, > the longer you stay stuck on a technology, the harder it is to migrate > afterwards. > You're reading something into my answer that I didn't say and definitely wasn't intended. I'm not suggesting we ignore the post-JDK 9 world, or as John said there isn't a technical debt to address, but that IMO the build should always by default always require an LTS in this brave new world, with the experimental option of later JDK's as a nice-to-have as we update towards future LTS. Yes, that requires contributors to have JDK 8 available, but I really disagree with you that this is much of a barrier. Lots of developers are not using JDK 9+ yet anyway, and I would expect most of those experimenting with it still have JDK 8 installed too. > Have you heard that Ubuntu 18.04 LTS will ship JDK 10 and bump it to 11 in > a point release? > Well, Ubuntu are kind of stuck between a rock and a hard place with dates there! Still, they're not planning on removing OpenJDK 8 either. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
