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.
Product Version = NetBeans IDE 8.0 (Build 201403101706) Operating System = Windows 7 version 6.1 running on x86 Java; VM; Vendor = 1.8.0_20-ea Runtime = Java HotSpot(TM) Client VM 25.20-b10 Hello, Well While creating the JavaFX project on netbeans 8.0 the compile on save option is disabled and locked specifically for JavaFX projects, for others it is not locked and is enabled, So because of this I have to use the option clean and build project again and again after making any changes on my code to see the effect.The alternative option for this was that one need to save and compile manually and then run the code file but even this is not working and enforcing to use clean and build option to run the project. So please help me to this issue and provide the solution for it. Thanks, Anurag
Created attachment 147860 [details] IDE log
Thanks for the report, however "Compile on Save" is intentionally disabled in Java FX project (running Javx FX project needs JAR assembled by javafxpackager). When you use "Run" action to run your project after you have made some changes, only changed classes will be compiled.
Hello, Yes When I use "Run" action to run my project after making changes, only my changed class is getting compiled but after compilation it still not showing the changes I made, It still showing the last output, So for seeing the effect of changes I made I have to use the "Clean and Build" option every time while making any changes. So please provide the solution of it and resolve this issue. Thanks, Anurag (In reply to Roman Svitanic from comment #2) > Thanks for the report, however "Compile on Save" is intentionally disabled > in Java FX project (running Javx FX project needs JAR assembled by > javafxpackager). > > When you use "Run" action to run your project after you have made some > changes, only changed classes will be compiled.
I can't reproduce the issue you have mention in comment #3. Changed class is compiled and changes can be immediately seen. If you still consider this as an issue, please add exact steps how we can reproduce the case when changes are not propagated after successful compilation of the class. Thanks!
I had the same "issue" as you and here is how I fixed it: 1. Open the file called "project.properties" that you can find inside the folder called "yourprojectname/nbproject". 2. Find the line where it says "compile.on.save.unsupported.javafx=true" and comment it out (add "#" before the line). 3. Make sure to save the changes you made on your "project.properties" file. I didn't have to restart the IDE because the changes were applied directly after and it worked.
This is not fixed. Rather, Rajojon23 has provided a workaround to set compile.on.save.unsupported.javafx=false. However, my understanding is that the default is purposely set to True as pointed out by Roman. @anurag.srivas - In fact, if the bug you described in Comment #3 is reproduceable, then you should please comment with the exact steps to reproduce so that it can be investigated. Otherwise it can't be Fixed. Therefore I am marking this issue as Incomplete, because it is not Fixed and is waiting for Reporter's response.
I was going to file a bug that exactly matches the summary. I assumed it was known but I wanted to understand the issues and when/if it would be fixed. I found this bug before filing a new one. I see it was marked incomplete for reasons other than the specified bug. I believe a new bug should be filed for this other issue. The original issue, can't turn on compile and save, still exists. (Maybe the summary should have been changed when it was marked incomplete) Is this a jdk7 vs jdk8 issue?
Is this issue being worked on still? I have come across this this evening and was led here in a search for an answer. I read in the comments that the status is Incomplete. I see you were asking for specific steps to create the problem. When I open the project properties and go to the Compiling tab, CoS is unselectable. Any ideas why this is? I'm working on a JavaFx project, I'm using Java 8. I have no idea if this is an issue in Java 7 and it seems irrelevant. Thanks for the assistance.
A final comment. I went back into the project properties, as I have 2 classes with main methods I went to the Run tab in properties and changed the Application Class field to the associated class that was connected to the issue. I made changes, pressed F6 and the class compiled and ran as expected and all changes were visible. However, CoS is still unselectable.
Actually, under the Build tab within properties I deselected build JAR after compiling, which I believe is the source of the problem. If you want to actually build the JAR go in and select it at that time. CoS still unselectable after modifying the project.properties file.
While "Run Project" (F6) works for me, "Run File" (Shift+F6) didn't until I applied the workaround#5.
(In reply to t_gergely from comment #11) > While "Run Project" (F6) works for me, "Run File" (Shift+F6) didn't until I > applied the workaround#5. @t_gergely: Please don't change the version. Reverting back to its previous value