prepare NB 19 release cycle for JDK 11.

[mbien]

• disable CV tests on JDK 8
• move some more jobs to JDK 11

this configuration would allow us to move new modules like rust/go/hcl to JDK 11 and to upgrade exiting modules, like the maven-indexer #4999.

new NB release policy

[neilcsmith-net]

todo: wiki link to new NB release policy

Sorry for the delay with that - https://cwiki.apache.org/confluence/display/NETBEANS/Minimum+JDK+build+and+run+policy

[jlahoda]

FWIW, there should be a PR at some point (not necessarily here) that would provide user friendly failure messages when the build or binary is used on an unsupported JDK.

[neilcsmith-net]

FWIW, there should be a PR at some point (not necessarily here) that would provide user friendly failure messages when the build or binary is used on an unsupported JDK.

Well, we've really needed that for the IDE since NetBeans 13!

Personally, I would now look to bump the bytecode level in non-API bits of the runtime container. eg. check and fail, and update the error messages, at https://github.com/apache/netbeans/blob/master/platform/o.n.bootstrap/src/org/netbeans/Main.java#L43

If as well as checking for JDK, we updated the bytecode level, it would also allow for removing some reflection in #3386 ?

[mbien]

@dbalek @sdedic this would move the NBVSCode ext and the LSP job to JDK 11 since those jobs load all other modules. If the VSCode Ext has different requirements we would have to change the test setup there.

But from past conversations I believe to remember that JDK 11 was no problem there, right?

[neilcsmith-net]

Follow up to brief comment on the Markdown PR.

Once we're ready for this, we should also add a new label for PRs that update the Java requirements for any module - "non-optional modules are free to adopt the minimum JDK as they need to." should be part of the review process. min-JDK-change ??

[matthiasblaesing]

Looks sane to me.

[mbien]

Once we're ready for this, we should also add a new label for PRs that update the Java requirements for any module - "non-optional modules are free to adopt the minimum JDK as they need to." should be part of the review process. min-JDK-change ??

@neilcsmith-net we have Upgrade Library Library (Dependency) Upgrade , how about just Upgrade JDK Upgrade to the JDK requirements of a module. ? We could explain it in the label tooltip.

FWIW, there should be a PR at some point (not necessarily here) that would provide user friendly failure messages when the build or binary is used on an unsupported JDK.

agreed

[mbien]

I got a thumbs up #5852 (comment) and one approval. So I interpret this as go-ahead -> merging.

[mbien]

@neilcsmith-net are you ok with the name of the new label?

[neilcsmith-net]

@mbien looks good. I don't really mind the name, as long as we have one and all know what it means! 😆

[mbien]

@vieiro @lkishalmi I remember from reviews that you both tried to use language level 11 before for rust and similar independent modules. This is now possible.

simply mark a PR with Upgrade JDK Upgrade to the JDK requirements of a module. so that we can track it and bump the source/target property for the module.

[vieiro]

@mbien I'm with with language level 8 at the moment. Good to know we can mark things for 11, though.

[mbien]

see #6054 regarding JDK requirements warning UI