On Tue, Aug 21, 2018 at 4:46 AM, Scott Palmer <[email protected]> wrote:
> This is not quite right. Anyone using the NB platform is not forced to > upgrade the platform they base their application on. The only thing that > happens is that the platform code base can hold them back as well from > building with new JDK features. > IMO the NB code base should support building on the latest released JDK > specifically because then it doesn’t hold others back that want to use new > Java features for their NB platform applications. But there's a difference between being able to be built on the latest JDK, and requiring the latest JDK to build/run. Regarding the LTS, while there may not be a (free) release from Oracle, it's still a symbolic line in the sand of compatibility that I would assume that the OpenJDK versions would track. i.e. OpenJDK v11 would be compatible with Oracle JDK v11 (for some spectrum of compatibility), and continue to track and sync with each other over time. That is, and I don't know, but is there any expectation that OpenJDK is going to be using its own versioning scheme? If that's the case, then "supporting JDK vXXX" brings on a completely different meaning if the implementations start to diverge. Regards, Will Hartung
