This content has been marked as final. Show 4 replies
Eclipse + the JBoss Tools plugin works flawlessly.
Don't blame the Netbeans devs, Red Hat/JBoss basically ignores its existence and bases their entire tool line on Eclipse. Thus if you want to use JBoss, I can highly suggest you make the switch. Of course then you have to deal with a lack of proper JavaFX 2 plugin, but nobody said programming was easy.
then you have to deal with a lack of proper JavaFX 2 pluginI haven't used it, but I'm sure e(fx)clipse is a capable JavaFX 2 plugin:
SceneBuilder integrates (somewhat) into eclipse as well:
Note that a dedicated plugin isn't strictly necessary for JavaFX development.
The current main benefits of the NetBeans JavaFX integration (in my opinion) are:
1. The ability to easily import and run all of the Oracle JavaFX examples.
2. A GUI for setting up packaging configurations for jnlp based deployments.
(e(fx)clipse also provides a, somewhat limited, GUI for this).
3. JavaFX css attribute and fxml code completion and syntax highlighting.
(e(fx)clipse also provides support for this feature).
If first class support for JBoss integration is vitally important to you, then you may be better off sticking to eclipse.
I am already using JBoss and eclipse. I was only trying netbeans to use the javafx facilities, but the JBoss version provided in the project creation task does not include JBoss-7. Beside, if you work for an organisation, you don't have the flexibility to change tools --The decision is not entirely yours.