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.
After updating javafx to 'Build-42' I could not give clean & build project inorder to generate the .html, .jar and .jnlp files. On giving clean & build project I get the following message, init: deps-clean: Updating property file: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\built-clean.properties Deleting directory C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build clean: init: deps-jar: Created dir: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build Updating property file: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\built-jar.properties Created dir: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\classes Created dir: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\empty Compiling 4 source files to C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\classes Copying 14 files to C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build\classes compile: Created dir: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\dist Copying 1 file to C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\build Nothing to copy. Building jar: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\dist\Balloon Game.jar To run this application from the command line without Ant, try: java -jar "C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\dist\Balloon Game.jar" check-jfx-deployment: jfx-deployment: Deleting: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\dist\Balloon Game.jar Deleting: C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\dist\README.TXT C:\Users\Isaac\Documents\NetBeansProjects\JavaFX 2.0\BalloonGame\nbproject\jfx-impl.xml:23: fxjar doesn't support the "applicationClass" attribute BUILD FAILED (total time: 2 seconds)
*** Bug 201777 has been marked as a duplicate of this bug. ***
The NB FX support plugin published at javafx.com as "javafx b42 NB plugin" is broken due to last minute changes of javafx deployment ant tasks. The whole plugin is getting complete overhaul. Please try to download the JavaSE package of NB7.1 nightly build from http://bits.netbeans.org/download/trunk/nightly/latest/start.html?platform=windows&lang=en&option=javase This package already contains the refurbished plugin. Note that to successfully crate a FX Project it is needed to first create a "FX enabled" java platform in NB Platform Manager.
How does one create an "FX enabled" java platform? Most people who were having this issue who read that weren't sure what you were saying they needed to do.
To create a New FX Application in NetBeans it is necessary to first manually set-up a "fx-enabled Java platform" (in later builds this will be done semi-automatically). This means creating a JDK platform with correctly assigned FX SDK - such platform is then used when executing the fx app. This mechanism is an extension of the standard mechanism of maintaining JDK platforms for Java projects (see Project Properties dialog, Libraries panel, Java Platform). This is to be done in NB Platform Manager. Note that because FX can not be enabled in the default platform (which is the one on which NB itself is running) you need to first Add Platform.. to create a new one. Once a new JDK platform is added, a new tab appears for it in Platform Manager called JavaFX. In this tab check Enable FX and fill the FX SDK, RT and javadoc fields using Browse.. (RT and javadoc fields should get filled automatically once you point at your FX SDK location). Now in the New FX Application dialog select the just created fx-enabled platform and Finish project creation. Now it is possible to Run or Debug. Note that with the current build (9 SEP 2011) generating all deployment files is possible only through Clean&Build. Please note also that although the project property dialogs contain various run options like "run in webstart"or "run in browser", these are still under development and are not functional yet. With the current build many other UI options do not propagate properly to deployment files yet, but we are just working on it and every other daily build improves in this respect.
Remark: there was a bug in yesterday's build that prevented running 23bit FX app when NB run on 64bit platform and vice versa. This should be fixed by now but the fix may not have propagated to today's build yet. http://netbeans.org/bugzilla/show_bug.cgi?id=201839
I followed your steps, but did not see an option for selecting a platform in the File->New Project->JavaFX Application dialog. So I created the project then set the platform by going to properties->Libraries and changing the Java Platform. I then copied all of my files from the other project into this new one, added the libraries I needed, then did a clean and build and I still get: C:...\jfx-impl.xml:23: fxjar doesn't support the "applicationClass" attribute I'm using NB build 201109090600
We have got reports about the missing JavaFX tab in Platform Manager (even with non-default platform). The reason appears to be the "features on demand" NB mechanism, i.e., the JavaFX tab does not show up as long as FX support has not been activated. Sorry for confusion, I did not realize this before. For this reason my description in #4 is confusing because it suggest first to setup fx-enabled platform and only then set-up new fx project. The right sequence is to start with creation of the fx project. So start with File->New Project->Java->New FX Application (of the item is grayed, it points at it being not activated yet). The opened New FX Application dialog identifies that there is no fx-enabled platform selected and offers to open the Platform Manager to define one. Now fx support is activated and the Platform Manager should show the JavaFX tab.
(In reply to comment #7) > We have got reports about the missing JavaFX tab in Platform Manager (even with > non-default platform). The reason appears to be the "features on demand" NB > mechanism, i.e., the JavaFX tab does not show up as long as FX support has not > been activated. Sorry for confusion, I did not realize this before. For this > reason my description in #4 is confusing because it suggest first to setup > fx-enabled platform and only then set-up new fx project. The right sequence is > to start with creation of the fx project. So start with File->New > Project->Java->New FX Application (of the item is grayed, it points at it being > not activated yet). The opened New FX Application dialog identifies that there > is no fx-enabled platform selected and offers to open the Platform Manager to > define one. Now fx support is activated and the Platform Manager should show > the JavaFX tab. I don't think I communicated what happened clearly: I successfully created a JavaFX enabled platform, even though I didn't do it through the new JavaFX Application dialog like your instructions said. The JavaFX tab showed up fine. I set my project to use that platform. I still get the error that prevents me from building. Are you saying that I won't get that error if I follow your steps (even though they both seem to have the same effect)? Furthermore, I can't even follow your steps. When I delete the JavaFX platform, then go to create a new JavaFX Application, nothing on the dialog tells me that there's no FX Platform. It just creates the project then shows the project as having a bunch of errors because it can't find the javafx libraries. Welp, that's what I get for using beta software for my research project. An inability to compile my program when I desperately need to compile it. It would be nice not to be punished for my stupidity, but such is life.
turns out I needed to completely uninstall my previous netbeans installation and now all those newfangled features are there
yeah, it's working now
I'm completely new to java, javafx and netbeans. Yesterday I had downloaded and installed: - javafx_apps-2_0-beta-b42-23_aug_2011 - javafx_sdk-2_0-beta-b42-windows-i586-23_aug_2011 - javafx-2_0-beta-b42-netbeans-30_aug_2011 - javafx-2_0-beta-b42-windows-i586-23_aug_2011 - jdk-7-windows-i586 - netbeans-7.0.1-ml-windows I generate and build a new project with netbeans. I get "error: cannot find symbol primaryStage.setVisible(true);" I change it to "primaryStage.show()" Now, I get "fxjar doesn't support the "applicationClass" attribute" How to go ahead? Where is a new version to install?
(In reply to comment #11) > I'm completely new to java, javafx and netbeans. Yesterday I had downloaded and > installed: > - javafx_apps-2_0-beta-b42-23_aug_2011 > - javafx_sdk-2_0-beta-b42-windows-i586-23_aug_2011 > - javafx-2_0-beta-b42-netbeans-30_aug_2011 > - javafx-2_0-beta-b42-windows-i586-23_aug_2011 > - jdk-7-windows-i586 > - netbeans-7.0.1-ml-windows > > I generate and build a new project with netbeans. I get "error: cannot find > symbol primaryStage.setVisible(true);" > I change it to "primaryStage.show()" > > Now, I get "fxjar doesn't support the "applicationClass" attribute" > > How to go ahead? > > Where is a new version to install? I'm not an oracle person, but I can tell you what I did to solve the problem. Delete your existing netbeans installation. When prompted, remove the settings. Go download a development build of netbeans (http://bits.netbeans.org/download/trunk/nightly/latest/). That build comes with javafx support already, so you don't need to install the javafx plugin. Now, create a new javafx project. When it tells you there's no javafx platform, go to the java platform manager, click add platform, navigate to the java sdk and use that. Click the javafx tab, then point it to the javafx SDK. Now, back in the project dialog, select that platform and finish. Fix the error if it's there (.show) and do a clean and build. It should work.
Thanks kwhipke1 for comment #12. I can remark that this will get simpler in one of the upcoming builds: (https://netbeans.org/bugzilla/show_bug.cgi?id=201800). I am now going to close this bug #201719 because it originally related to a no-longer supported code which is unfortunately still accessible at javafx.com for download as "JavaFX 2.0 Beta Plugin for NetBeans IDE 7.0 (build 42)". This code has been replaced by a differently designed FX support being developed as part of NetBeans 7.1. This fact will be communicated at javafx.com soon. So for the time being use the link http://bits.netbeans.org/download/trunk/nightly/latest/ to obtain the latest NetBeans build where updated FX support is integrated. For any issues related to the updated integrated FX support in daily NB builds please file new bugs whenever needed.
(In reply to comment #12) > (In reply to comment #11) > > I'm completely new to java, javafx and netbeans. Yesterday I had downloaded and > > installed: > > - javafx_apps-2_0-beta-b42-23_aug_2011 > > - javafx_sdk-2_0-beta-b42-windows-i586-23_aug_2011 > > - javafx-2_0-beta-b42-netbeans-30_aug_2011 > > - javafx-2_0-beta-b42-windows-i586-23_aug_2011 > > - jdk-7-windows-i586 > > - netbeans-7.0.1-ml-windows > > > > I generate and build a new project with netbeans. I get "error: cannot find > > symbol primaryStage.setVisible(true);" > > I change it to "primaryStage.show()" > > > > Now, I get "fxjar doesn't support the "applicationClass" attribute" > > > > How to go ahead? > > > > Where is a new version to install? > > I'm not an oracle person, but I can tell you what I did to solve the problem. > > Delete your existing netbeans installation. When prompted, remove the settings. > Go download a development build of netbeans > (http://bits.netbeans.org/download/trunk/nightly/latest/). > That build comes with javafx support already, so you don't need to install the > javafx plugin. > > Now, create a new javafx project. When it tells you there's no javafx platform, > go to the java platform manager, click add platform, navigate to the java sdk > and use that. Click the javafx tab, then point it to the javafx SDK. Now, back > in the project dialog, select that platform and finish. Fix the error if it's > there (.show) and do a clean and build. It should work. Thank you! It worked immediatly and said "Hello World!"