On 16.10.22 17:13, Michael Bien wrote:
On 16.10.22 16:05, Matthias Bläsing wrote:
Hi,
Am Sonntag, dem 16.10.2022 um 13:12 +0200 schrieb Michael Bien:
just to clarify: it doesn't even have to be an installer, NB itself
could check during boot if the runtime JDK meets the requirements, and
if it doesn't -> offer to download one which does.
why do you want to destroy the ease of the OS independed ZIP? Currently
I can use NetBeans with OpenJDK 11 or 17 (I have both installed) and it
just works.
the zip would be the same as today. It would be still OS independent,
it would not contain the JDK. The difference would be that NB would
complain and offer to install a current JDK on launch _if_ the
requirement is not met.
As first step it would complain if you would try to start NB on 8 and
recommend 11+. The user could still press cancel and set JDK home in
some other way. But the user could also use the wizard to download a
new JDK from a vendor of choice or select one which is already
installed somewhere.
And some time down the road, _if_ we do decide to remove nb-javac to
simplify our whole setup (and get all the advantages of a new JDK). We
could. All we would have to do is to bump the requirement from 11+ to
current-at-release and remove the nb-javac dependency, simplify CI,
build, get all the goodies etc.
The same mechanism could even offer to update NB itself to the next
major version. Zip on steroids ;)
Where do you draw the line? The javac interface is not API, so you'd
need to tie the NetBeans installation to a single JDK and vendor. This
raises question about bugfixing and security of the chosen JDK. For me
this does not fly.
The javac interface is actually API, its just not stable if you hook
into internals, esp between major releases.
https://docs.oracle.com/en/java/javase/19/docs/api/jdk.compiler/module-summary.html
I am actually doing this since quite a while already. I run NB on the
javac of the JDK while having nb-javac not installed. I haven't
experienced incompatibilities between JDK minor update releases so
far. The JDK major version would have to match, vendor and minor
shouldn't matter.
if bugs are a concern we could even consider to join
https://wiki.openjdk.org/display/quality/Quality+Outreach
this would further reduce the probability that a OpenJDK update would
break NB.
-mbien
best regards,
-mbien
Greetings
Matthias
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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