On 15.04.22 06:56, Jaroslav Tulach wrote:
NetBeans 13 already doesn't require nb-javac if you run on JDK 17, its
only remaining purpose is to allow users to run NetBeans on older JDKs.
Given the javac API (including trees API & other internals as used by
NetBeans) isn't developed in a compatible way, it is not guaranteed at all
NetBeans 13 can use javac from newer JDK than 17. I suggest to rephrase as:
NetBeans 13 already doesn't require nb-javac if you run on JDK 17, its
purpose is to allow users to run NetBeans on other JDKs than 17.
-jt
my original mail was a bit longer, I removed a few things to keep it
simple. I think its clear that running NetBeans with libraries which
weren't there on release has to be done on your own risk. Generally: you
should not do that. Instead consider using a dev build of the next NB
release. But if all you want to do is to experiment with an upstream JDK
release for a few hours, running NB with the upstream javac temporarily
works often good enough in my experience.
Jan added recently some improvements which might not even require to
change anything at all (in some situations)*.
The point i wanted to make as reply to the original question was that
there is nothing special about nb-javac (anymore, it used to be the
case). Its a recent javac snapshot automatically backported to a lower
language level. If the reader understands that, everything else can be
hopefully inferred.
we probably should put that into an easily linkable FAQ somewhere
*https://github.com/apache/netbeans/pull/3598
-mbien
---------------------------------------------------------------------
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
