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.
Cannot debug in a new created javafx application using jdk1.8 102. I tried Netbeans 7.4beta and some nightly builds up to 201308152300. Only tried on MacOS X 10.8.4. I go to File > New Project > JavaFX Application I assign the JavaFX platform to JDK 1.8 and hit finish When I run the newly created project, the program runs BUT when I debug into (set breakpoint an hit debug) it I get a window titled "JavaFX Launcher" with the following message: "This application requires a newer version of the Java runtime. Please download and install the latest Java runtime from java.com. Then restart the application." Might be duplicate of 231756 but they reported a fix for Windows 64
I forget: Netbeans itself uses jdk1.7.0_25
I can confirm this issue on Win7 x64 + JDK8 b103, NetBeans Dev 20130815.
Issue is present only when IDE is running on JDK7 and FX Project is using JDK8. When IDE is running on JDK8, debugging works without problems. It seems that when JAR is created in NetBeans running on JDK7, then classes from package com.javafx.main from JDK7 are packed into jar.
I am renaming this so it will have a more meaningful title when seen in a list. "Cannot debug when IDE is running on JDK7 and FX Project uses JDK8"
Pinging up, as this is still the case in 7.4 GA. Running instead of debugging works fine. Debugging seems to pick the wrong platform.
*** Bug 237579 has been marked as a duplicate of this bug. ***
Issue is not reproducible in the latest DEV build + JDK 8 b116. It seems that some issue in JavaFX packager has been fixed and it does not cause the problem with debugging anymore. Someone please verify whether the issue can't be reproduced or it it possible to reproduce it in some way. If you'll manage to reproduce behavior mentioned in this bug report, please reopen this issue and post steps how it can be reproduced in the latest dev builds with latest JDK8 build. Thanks!
Issue is not reproducible in the latest DEV build + JDK 8 b120.
Also verified works in 7.4-patch2