This is the third attempt to get my pull request accepted and integrated, after#94 and#122 were declined, and a feature proposed in#122 was later integrated in#255.

The commit I am asking you to integrate allows for three further bundler parameters:

• jnlpTemplates -- a list of HTML files to be processed as templates byJNLPBundler
• title -- a title to be used by any supporting bundler, and which defaults to${project.name}
• description -- a description to be used by any supporting bundler, and which defaults to${project.description}

Although@FibreFoX has integrated the option to specify<bundleArguments> andjnlp.templates is aStandardBundlerParam, cf.JNLPBundler, such a list of files cannot be parsed from thepom.xml, since a String converter is missing, seeJNLPBundler. My solution to this works as follows.

1. An optional list-valued fieldjnlpTemplates is defined in theNativeMojo.
2. A user may add several<jnlpTemplate> entries (within<jnlpTemplates>) pointing to files to be used as templates by theJNLPBundler.
3. When executingNativeMojo for the bundlerjnlp, then thisList<File> is converted into aMap<File,File>, see Lines 757-765, and theMap<File,File> is then added toparamsToBundleWith with keyjnlp.templates.
4. After a successful execution of theNativeMojo, the processed HTML files can be found intarget/jfx/native.

In case one needs further control on where to output and store the processed HTML files, one could extend the fieldjnlpTemplates to allow for the declaration of pairs of input and output files. Currently, it is only a list of input files the names of which are used as names of the output files undertarget/jfx/native.