The Maven JavaFX Application template should use the Maven JavaFX Plugin (see  & ).
There are plenty of advantages:
* only this single plugin is required
* much better performance
** the current pom packs everything into a single .jar, which is very time consuming
* much better robustness
** packing everything into a single .jar is error-prone
** the current pom does all kinds of modifications of the classpath to add jfxrt.jar to it
** the current pom uses the now obsolete javafxpackager
** the current project requires customizations of the Run/Debug actions (in nbactions.xml file)
This is the whole <build> section of my current pom:
The only tricky part may be how to select the right version of the plugin, based on the JDK used for the project (see , under "Support for 8u20").
The fundamental problem with the current template, is that it's built to work with Java 7. I think a Maven JavaFX project should require a Java 8 platform. This would allow to greatly simplify the POM template.
Contrary to what I said in my first comment, I don't think it should use the Maven JavaFX Plugin. The current POM is ok, but the invocation of javafxpackager should be replaced with an invocation of javapackager.
Also the "unpack-dependencies" part should be eliminated: it's extremely time-consuming to do on each build & is not necessary either: with Java 8 you can just do "java MainApp" (where MainApp extends javafx.application.Application & does not have a main() method), as with any other class. This also means there should be no need for a special nbactions.xml file.
Also there should be no main() method in the generated JavaFX Application class (see bug 249887).