This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
we can not use recent netbeans, it fails to start. Please, make something with javafx to be conditionally required and not forced to be present. #java -version java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) Server VM (build 24.45-b08, mixed mode)
Created attachment 142690 [details] message.log Exceptions and fails to start
Created attachment 142693 [details] Threads dump during freeze other time it just hangs forever on splash screen
The javafx support does not link to javafx.jar. It just uses it as a library on project's classpath. Also according to the log the javafx cluster not even enabled.
Result of issue 237973. Also influences openjdk (which comes without JavaFX) - reported as bug 238676. The fix will likely check whether JavaFX is present and if not it will disable org.netbeans.libs.javafx module and all modules depending on it. An access to Solaris machine would be helpful for reproducing the problem, guys: pls send me some VNC/ssh info. As there is not going to be JavaFX for Solaris, it seems that we cannot use JavaFX for any essential UI. Alas, that was exactly what I planned to do.
Thanks for the access to the Solaris machine. I downloaded http://smetiste.cz.oracle.com/builds/netbeans/trunk/latest_daily/zip/netbeans-trunk-nightly-201312020002-cpp.zip unzipped it and (while some exceptions are printed during start) it runs reasonably OK - I can see the New Project dialog with appropriate content.
Comments? As I said, I see some exceptions in console but NetBeans runs fine. Making P4 to provoke a quote.
tested today's build. NB doesn't start. After splash screen it exits. Message.log will be attached.
Created attachment 142806 [details] IDE doesn't start
I will send you privately access to my Solaris
it works in VNC and doesn't work in real Solaris
I tested the behavior on openjdk and improved it to properly warn the user: ergonomics#16c8219acb86 Can you guys please check the patch on Solaris? I have not seen the cyclic failure yet...
Thanks, IDE runs now. Remaining problem is "NetBeans IDE - Warning" dialog which suggests to download JDK from Oracle for JavaFX which would confuse Solaris users which have Oracle JDK by default, they just don't have JavaFX (and will not have)
The other problem is that Warning dialog suggests to Disable Modules and Continue (which is fine). But it appears not only with fresh userdir, but on any next runs as well. So, looks like module is not disabled
Btw, on the second and following starts I see about 5 java.lang.IllegalStateException: no splash screen available at java.awt.SplashScreen.checkVisible(SplashScreen.java:192) at java.awt.SplashScreen.update(SplashScreen.java:302) at org.netbeans.core.startup.Splash$SplashPainter.repaint(Splash.java:399) at org.netbeans.core.startup.Splash$SplashPainter$2.run(Splash.java:514) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Created attachment 143214 [details] Introducing org.openide.modules.jre.JavaFX token The best way to avoid the dialog is to use different dependency than "package". The package one is checked too late and results in slow down of the start sequence as well as in showing a dialog. I propose an introduction of new token (provided by core module system) that modules like libs.javafx can depend on. This token guarantees the check is done early and if JavaFX JAR is not present, the dependant modules are disabled silently.
There don't seem to be any objections, so I'd like to integrate before I leave for Christmas break.
sent to ergonomics repository to build before merge: changeset: 09fc30e29401 tag: tip user: Jaroslav Tulach <jtulach@netbeans.org> date: Wed Dec 18 15:48:15 2013 +0100 summary: #238939: Introducing special token to trigger on modules that require JavaFX. Mitigates missing jfxrt.jar on Solaris.
http://hg.netbeans.org/main-silver/rev/113854e1a1d5
Integrated into 'main-silver', will be available in build *201312210002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/09fc30e29401 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #238939: Introducing special token to trigger on modules that require JavaFX. Mitigates missing jfxrt.jar on Solaris.
thanks!