Thanks for sharing your workaround
The plugin is supposed to work with Oracle/Sun JDK 6, but because of this javafx dependency, it fails working out of the box
I am asking if javafx should not be exclude from the dependencies of the maven plugin.
Prior to version 5, SoapUI relied on teamdev jxbrowser for browsing features and jxbrowser dependencies were excluded from the plugin dependencies. So I guess, they were not usefull to run the plugin, especially because in that case, we do not use browsing. As javafx is now used in place of jxbrowser, I guess it should now be excluded.
