Bug 213572

Please consider adding the ability to add entries to the automatically created manifest file for javafx projects.

Posible Solution:
A simple solution like what was done for the javafx params and arguments would be great. This would allow something like the following added to the project.properties file to add entries into the manifest:
javafx.manifest.1.name=test-line
javafx.manifest.1.value=test-value
javafx.manifest.aa.name=test-name
javafx.manifest.aa.value=testing

The jfx-impl.xml macrodef for deploy-jar already has some javascript in the fx:param, fx:argument section that could be adapted to allowing entries to be added to the manifest file. The javafx.manifest.* project properties would simply be ignored for the macrodef deploy-deploy since no manifest file is created.

Reason for request:
I am creating javafx library jar files that will be dynamically loaded a standalone javafx app (ie: no jnlp or web). I would like the ability to read the manifest to get information about the jar that I may dynamically load. I realize there are other ways to skin this cat but the manifest seems the easyiest to me (the JarFile class already does the heavy lifting).

Thanks,
SLDR
(Stephen L. De Rudder)