I don't want to leave this old thread open without a status report:
- gradle module is up2date and is now pulling the files from the
official gradle server thanks to Laszlo and Matthias
-> https://github.com/apache/netbeans/pull/3326
- Java cluster is buildable on JDK 17
-> https://github.com/apache/netbeans/pull/3278
-> https://github.com/apache/netbeans/pull/3372
- nb-javac is pulled from maven and included by default, which makes
javac 17 the new baseline if i see this correctly
-> https://github.com/apache/netbeans/pull/3251
-> https://github.com/apache/netbeans/pull/2783
whats left:
- a lot of tests won't work without solving the OSGI issue (I suppose
"netbinox" isn't relevant at runtime otherwise we would have noticed it
by now while running on JDK 17)
- JDK 17 doesn't have the javascript runtime
- "Replacing SecurityManager with a tracking agent" sounds super
interesting for JDK 17+
-> https://github.com/apache/netbeans/pull/3386
good job everyone!
-michael
On 10.11.21 19:42, Michael Bien wrote:
Hello,
I got encouraged by Neil to start a new thread - its not my fault.
current status:
JDK 11 is the latest non-EOL JDK, NetBeans can be build or tested on.
Building NB on JDK 17 involves most likely just a few property bumps
and library updates. I could make the java cluster build just by doing
that and by updating the build-time gradle wrapper.
(https://github.com/apache/netbeans/pull/3278)
I can't actually update the gradle wrapper myself (outside of making
it point to a local zip for testing purposes) because i am not
familiar with the lib hosting service the NB build uses - that is why
its not part of the PR - someone else would have to do that (why can't
it just use a maven repo?).
That would be the easy part, testing on JDK 16+ is going to be more
interesting, since NetBeans appears to hook into a very old version of
osgi (3.9 via the netbinox module and friends as far as i see, which
doesn't even officially support JDK8 btw). There need to be also some
updates to junit JVM flags and build configs, but i have those in my
stash and it isn't really worth mentioning, beside that its all over
the place as to be expected in a big project. Using JDK 16 as a
intermediate step before progressing to 17, might help there since the
module system of 17 became more restrictive on top of all that.
If NetBeans 13 would like to claim to support JDK 17 i would recommend
to start with some of this early in the development cycle, esp with
the low hanging fruits (gradle wrapper, which unblocks the
build-java-cluster-on-17 PR etc).
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
