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.
| Summary: | Compile, run single don't work | ||
|---|---|---|---|
| Product: | javafx | Reporter: | Martin Ryzl <mryzl> |
| Component: | Unsupported | Assignee: | Adam Sotona <asotona> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | Keywords: | RELNOTE |
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
Martin Ryzl
2008-10-17 11:18:25 UTC
compile and run single should be well specified and then implemented as a new feature *** Issue 149249 has been marked as a duplicate of this issue. *** *** Issue 149930 has been marked as a duplicate of this issue. *** I've fixed it in trunk. Compile Single invokes Compile Project and it is always enabled. Run Single and Debug Single overrides Main Class and then invokes Compile Project or Debug Project, both are enabled when exactly one JavaFX source of the project is selected. "Run Single and Debug Single overrides Main Class and then invokes Compile Project or Debug Project, both are enabled when exactly one JavaFX source of the project is selected." Is this the final fix ? I mean, compile et rebuilt the entire project for each test can be (and for me it is) a very heavy and long process. Do you plan to re-implement the "Compile/Run single file" feature as it was implemented in NB 6.1 ? Thank you Real compile-single is unsupported as the compilation of the application is very complex multi-staged process. Compile-single action now invokes project compilation with current source set as main. This workaround is the only way we can guarantee the right compilation for all cases in all supported JavaFX profiles. JavaFX Packager (which is the provider of compilation) is planning to introduce an option to skip the whole part of the build process. We will leverage this option for compile-single action if necessary (from performance or any other reason). But run-single still must go through the whole building and packaging process. BTW What is your real use case, why do you need to manually invoke compile-single so frequently? Isn't the editor error annotation sufficient? Thanks, Adam In fact, I am currently porting an application from "preview" to 1.0, and I has been obliged to translate all my sources before beginning the tests. I'd had prefer to test "file by file" because I wasn't sure to do right in the new syntax. Now, I have made several changes in several files, and I have to perform all the test at the same time. As a workaround, I made several little projects to test the modifications. The editor error annotation is sufficient for syntax and semantic errors, but, of course, gives no indication on the program validity. Finally, my application will run as Web Start : Do the whole jar signing process run each time I build the project, as it seems according to my first try ? If I remember well, in 6.1, I could build the main jar without re-signing the other libraries (except if I made a clean). Thanks verified |