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
