On 06.03.22 16:06, Jaroslav Tulach wrote:
But as you pointed out some modules which are used by the language
server have to be kept compatible with 8 unfortunately, which causes a
lot of ongoing issues but it is what it is.
Can I get pointer to the list of "lot of ongoing issues", please? Thank you.
I don't know of any readily available list, but there is a lot of energy
spent to maintain compatibility with JDK 8. Dropping it fully would make
everything easier, CI included.
But to pick a concrete (while random) example: lucene 9.x only supports
JDK11+, the maven indexer modules are stuck with 5.x, updating it to 8.x
might require manually patching a certain bugfix form 9.x to 8.x since
there are no new releases planned for 8.x.
Which means we are stuck there - just because of the JDK 8 requirement
of some modules - unless we spend extra time and effort to find
workarounds and make it somehow work.
That is what i mean by ongoing issues. In other words: extra work caused
by technical dept.
i can't even vote on it since i am a mere contributor, but am sure
someone could setup a vote for the second part if there is demand, but
the first decision was already made (here on the list) and the releases
are public.
Yes, the decision is: the tests must run on JDK8. If you disagree with my
statement, present an evidence: show me where a decision to drop JDK8 for
(automatic) testing has been made!
I didn't disagree with your statement. Some tests need to run on JDK 8
to make sure that for example the requirements of the VS code netbeans
plugin are met. While NetBeans 13 binaries from Apache require JDK 11 or
17 to run - its in the readme :)
best regards,
-mbien
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
