> >> https://github.com/apache/netbeans/issues/4904 > >> > >> see also 'priority:high' label for more, > > > > The issue says "Many tests fail on JDK 11" - how does that compare to JDK > > 8? > well. You mostly see this while trying to fix them. It always requires > extra work to keep supporting 8 too.
The "extra work" is "keeping the code that already works"! We have code that works on JDK8 and there is no "extra work" to let it run on JDK8! Adding one additional `if (JDK11+)` check and writing new code is the "extra work", but it has nothing to do with supporting JDK8! > > I am a guy who cares about compatibility (of NetBeans): Please tell me if > > there is a test that doesn't work on JDK 8 and needs to be fixed. I am still willing to maintain JDK8 tests, CI & etc. > With every new JDK release it will become more difficult to keep > supporting JDK 8 as runtime. No. That is not true. The code exists and works. You don't have to do anything special to continue support it. > It also becomes increasingly difficult to > motivate myself to fix JDK 8 issues in my freetime. I can imagine that. However we are not coding NetBeans to please ourselves, but to please our users. NetBeans Platform users need JDK8 support. That's why I am volunteering to maintain and run the CI & tests on JDK8. -jt > If I see PRs which > fix edge cases in java-version parsing code which could be already > solved by simply using the JDK 11 API for it, I am just asking myself: > why are we doing this? It is not one thing which is the problem, its a > million paper cuts. > > -mbien > > > [1] https://www.eclipse.org/lists/jakartaee-platform-dev/msg03898.html --------------------------------------------------------------------- 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
