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.
(This assumes you have NetBEans 7.3 installed with JavaFX activated and a "Default JavaFX Platform" listed in Tools>>Java Platforms winch points to a jdk1.7.0_17 installation.) 1. Install JDK 1.7 Update 21 and set JAVA_HOME to this and add to path %JAVA_HOME%\bin. 2. Install NetBeans (all version) and use new userdir & cachedir. (Edit netbeans.conf and set "netbeans_jdkhome" to point to jdk1.7.0_21 if using zip version is JAVA_HOME is not set to jdk1.7.0_21.) 3. Run NetBeans and choose to import 7.3 settings. Activate Tools>>Options>>Java>>JavaFX then click OK. 4. Create new File>>New Project>>JavaFX>>JavaFX Application and click Finish button. 5. The project java file opens in editor and there are red error badges all over and under the Project context menu>>Libraries there is a broken. reference to "javafx.classpath.extention". 6. Open Windows>>Output and do a Build on the project. 7. Closing and opening project does not help and neither does restarting NetBeans. 7. Build is fine and all the file errors go away. If we open the Project Context Menu again the broken reference to "javafx.classpath.extention" is now OK. Workaround: Build project and errors go away. This does not occur any longer when creating a new JavaFX application after building the first project. Product Version: NetBeans IDE Dev (Build 201305102300) Java: 1.7.0_21; Java HotSpot(TM) 64-Bit Server VM 23.21-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_21-b11 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
In NetBeans 7.4 substantial internal changes have been made in FX related Project and FX related Java Platform support that are visible to users mainly by the removal of "FX-enabled platforms". The bug reported here was present in the daily build a couple of weeks ago but should be fixed by now as result of more implemented changes (esp. by Issue #229705). Accordingly I could not reproduce the bug with current daily build. Note that in NB7.4 when opening a project created in previous versions, any reference to "FX-enabled platform" is removed from project metafiles, being substituted by direct references to FX artifacts within the project's active Java Platform. These references are automatically kept up-to-date as long as the project is worked on in NB7.4+ (e.g., when Java Platform is changed). This mechanism improves and simplifies user experience in the current NB version, but imposes limits on backward compatibility. When 7.4 project is later opened in older NB version, bogus warnings and other minor problems can appear.