Hi, from my POV it is a fact, that NetBeans (the IDE) can't be required to be runnable on JDK 8 and in fact it is not. So my idea:
- commit to make NetBeans runnable on JDK LTS -1 - build with JDK LTS -1 - be able to be build with the current JDK - allow modules to depend on libraries, that require newer JDKs (see new JakarataEE developments for example, OpenJFX) - keep as many modules as feasible compatible with release 8 - if a module needs to break compatibility with java 8 it is the job of people wanting it to stay compatible to do the necessary work - the more to the core, the better the arguments for breaking compatibitly should be The idea here is, that I see Jaroslavs point that libraries should be compatible and I'm willing to sacrifice syntactic sugar for compatibility. What I won't accept is that we are stuck in the past. OpenJFX has a webbrowser and thus quickly becomes a security component, we must be able to update this. This also introduces a baseline java version: The absolute lowest support java version is the one still supported by the most current JDK. Greetings Matthias Am Dienstag, dem 10.01.2023 um 15:16 +0100 schrieb Michael Bien: > Hello devs, > > I hope everyone recovered from the last JDK 8 thread and is ready for > the first JDK 8 thread of 2023 :) > > The commit validation job is currently testing on 8, 11, 17 and 20-ea. > It doesn't like NetBeans editor modules which require java 11 though > which blocks a Jakarta EE 10 PR atm (#4692). > > This means we need either 1) a volunteer who would like to spend time > and fix JDK 8 tests, 2) we remove JDK 8 from the CV test matrix or 3) we > won't be able to merge this pr before freeze. > > Given that NB doesn't really support running on JDK 11 since a while I > would simply opt for 2) and merge. > > The problem is that I don't know the NB VSCode Extension situation very > well. > > Have the NB VSCode Extension specific tests (which run on JDK 8) > sufficient coverage so that we can remove JDK 8 from the CV test matrix? > At what point will JDK 11 modules become a problem for VSCode? When will > the VSCode NB extension bump the runtime requirement to 11? > > The next modules which would require JDK 11 are probably maven related > (#4999) but this wouldn't be for NB 17. > > best regards, > > michael > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
