#176986, #176912
Petr Nejedly <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.reviewers |
|---|---|
| Message-ID | <[email protected]> |
There were exceptions all over the place if you installed the full build and immediately started with a javafx project. It was caused by the fact that javafx editor uses some resources from java editor, but haven't had the dependency in it declared. The fix simply added the dependency, which should cause FoD to enable the java editor module too, when enabling the javafx kit. There was no such problem in other builds or when the java support was completely enabled. This was a showstopper as it made first hand experience with javafx dissasterous. The fix is safe as it doesn't really change the code, only instruct the platform to provide more support when javafx is to be used. The diff is: http://hg.netbeans.org/javafx/rev/4f4ec502e950 -- Petr "Nenik" Nejedly, Sun Microsystems, http://www.sun.com 355/113 -- Not the famous irrational number PI, but an incredible simulation!