What is the state of JavaFX Deployment?

Question

I did a search for deployment, self-contained apps, etc and found not a single thread in this forum about these topics.
I watched Mastering Java Deployment from JavaOne 2012 and I've proposed that my company leverage these technologies for our product to simplify our deployment to Enterprise customers.
I've done a lot of reading of the Java Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) but it appears to have been abandoned when Igor Nekrestyanov left Oracle for Intel in Nov 2012.
Here is the latest update from that blog:
+"> fx:platform doesn't support the "basedir" attribute+
+Please use JDK8 builds from http://jdk8.java.net/download.html+
+Due to change of release plans some changes had been postponed till next 7u update and will NOT be available in 7u10. Packaging changes are among them.+
+Posted by Igor on October 29, 2012"+
Specifically what features were postponed out of Java 7u10?
It just says 'packaging changes'?
Which packaging changes were postponed?
If we plan to use JavaFX packaging to create a self-contained app from a Swing application, will that not work in Java 7u10 and is it implemented in the current JDK 8 builds?
Can you confirm whether or not this will work in any version of Java 7?
There is now more up to date documentation here (http://docs.oracle.com/javafx/2/deployment/jfxpub-deployment.htm). It says last update was April 2013, but indicates that the information applies to JavaFX 2.2.21 and not JavaFX 8. It covers self-contained applications and using JavaFX in Swing applications, but it is not completely clear to me that packaging Swing applications with JavaFX 2.2.21 is supported.
Where can I go to find the latest updates on JavaFX deployment now that the Blog is dead?
Will there be talks at JavaOne 2013? I really need to get updates on the latest state of JavaFX deployment before then.
Note: I posted comments on the blog and was told that I had to wait for moderator approval, but it has been many days now without those comments being posted. So I'm not sure that there is an active moderator.
Thank you.

Answer 1

@bouye
If you have time, you may wish to create feature requests against the deployer in the JavaFX jira for some of the items in your post.
Note that some of your requests such as pre-post packaging scripts might not ever be implemented in the deployment tools (or would only be implemented as a loose shell like the maven rpm plugin), but might be delegated to some of the package specific packaging tools which the JavaFX deployment tools delegate too (for example the rpmbuild tool for rpm scripts).
While the JavaFX 2 branch is pretty much receiving very few updates now and most of the development effort is on JavaFX 8, I think a bunch of fixes and feature enhancements to the deployment tools will be added in a forthcoming JavaFX 2.2.40 release.  There are 55 deployment issues addressed for 2.2.40.  Some of those fixes were performed six months ago, so it is frustrating that it takes so long for Oracle to officially release them - they did seem to be making such good progress on this a year ago.  If you accept or work around some of the warts in the self-contained application packaging process, the tools work pretty well (at least for me).
You can also find the deployment issues scheduled for Lombard (JavaFX 8.0).  Most of the stuff you mention is not in there I think, also I think a lot of the deployment tasks which are not currently completed will likely end up getting dropped from the Lombard release as JavaFX 8 goes through a feature freeze and restricted high priority bug fix lockdown.
It may be worth investigating 3rd party tools such as the JavaFX maven plugin or JavaFX gradle plugin, you can log feature requests (or contribute code) against those projects for additional features you require - the features might end up getting deployed quicker (as long as capable people are willing and have time to work on them) than trying to integrate into the main JavaFX deployment tool code.  The JavaFX maven plugin has picked up 54 stars and 13 forks on github, so it is a mildly active project.