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). Do we need to somehow move JavaFX back to being recommended, not required? The features-on-demand support doesn't handle problems with external required dependencies gracefully at all. There are other issues triggered by this too, including another potential blocker with ASF policy on handling of optional Cat X dependencies - above also makes it appear impossible to cancel acceptance of JavaFX license. We have neither consensus on a way forward, nor consensus that this is actually a blocker. It would be good to try and reach both! Further info on JIRA issue and linked in issues - https://issues.apache.org/jira/browse/NETBEANS-4328 A quote from NETBEANS-3810 I agree with, where downloading failed due to network problems - "missing JavaFX and nb-javac should not be a blocker for project importing or creation ... If they are, they should be bundled with NB. Developers are not lawyers" Best wishes, Neil --------------------------------------------------------------------- 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
