Hi, Am Mittwoch, den 20.05.2020, 09:08 +0100 schrieb Neil C Smith: > On Tue, 12 May 2020 at 12:02, Neil C Smith <[email protected]> > wrote: > > .. I was just testing ... 12.0-beta4 ... and noticed a > > potential blocker issue. > > .. > > When importing settings from a previous install a dialog appears to > > install [JavaFX and nb-javac] > > that gets stuck in a loop if you try to cancel it. > > OK, following up on this here, as requested by Geertjan. > > We have multiple possible blocking issues in play triggered by a > change that has made the JavaFX download required by Java support > (actually added in 11.3) > > The most critical in my opinion is an effective lockup of the IDE on > first run when the user is unable to establish a network connection to > download JavaFX (or nb-javac) support from osuosl. We have multiple > JIRA issues already reported against 11.3 for this (where the problem > was introduced). >
this is not true. The problem exist since the first release of Apache NetBeans. nbjavac was required on all JDKs and is now required on JDK 8. It is by far "recommend", but required. So if nbjavac did not magically reach the system of the user, it was downloaded. If I'm not mistaken the same was true for the js parser, not sure when that was replaced by the UPL licensed version. With the addition of JavaFX the situation got a bit worse, but only gradually. If we could just bundle our dependencies ... The download for JavaFX comes from maven central (yes I know, that even maven central is down at times). >From my perspective NetBeans works as well as for example a maven build works, that has dependencies not yet present in a local repository. Greetings Matthias --------------------------------------------------------------------- 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
