#176993

The issue is that the debug action on a javafx project started some 
activity, but didn't really invoked the application to debug and just 
let the ant process running. It only happened in the full IDE with just 
the javafx cluster enabled and was caused by the fact that additional 
parts of the java infrastructure are necessary at runtime, without a 
compile time dependency. If the java cluster was enabled too, it worked 
well.

This is a showstopper as it completely breaks the javafx debugger 
functionality.

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 - adds a 
dependency on java.kit, forcing enough modules in to start working.

The diff is in this nicely numbered changeset:
http://hg.netbeans.org/javafx/rev/333332e08b48


-- 
Petr "Nenik" Nejedly, Sun Microsystems, http://www.sun.com
355/113 -- Not the famous irrational number PI, but an incredible
simulation!