jfx:native - MSI installer change request

[Scott Lewis]

Yes, a pass through would be just fine.  I don't think the order 
matters, if there's a way I could just pass in the "-ext WixUIExtension" 
parameter, that would suit our needs just fine :)

On 10/01/2014 04:10 PM, Danno Ferrin wrote:
> Would a "pass through" of certian command line arguments work?
>
> I'm not terribly familiar with WiX but does the order of the command line arguments (other than the relative order of the same command) matter?  i.e. if we insert a user supplied string at a single point would that get you as far as you need?
>
> On Oct 1, 2014, at 3:04 PM, Scott Lewis <scott.lewis at nsidc.org> wrote:
>
>> My apologies, I overlooked that this project has a JIRA tracker.  I'll file this request there.
>>
>> Scott
>>
>> On 10/01/2014 03:59 PM, Scott Lewis wrote:
>>> When I was using the jfx:native maven goal to create an installer for
>>> Windows using MSI, most of it works fine.  However, I wanted to
>>> customize the dialogs that are shown during the installation process.  I
>>> can get the configuration files OK, but the problem is that in order for
>>> it to work completely, the WixUIExtension needs to be included in the
>>> command line (using an "-ext WixUIExtension" option).
>>>
>>> Unfortunately, there is no way to add this when running the installer.
>>> The code (WinMsiBundler.java) hardcodes the WixUtilExtension, but that
>>> is all.
>>>
>>> Ideally, it would be nice to be able to specify any number of arbitrary
>>> extensions at the command line, perhaps via some kind of flag like
>>> -Dextension=WixUIExtension, which then gets passed into the
>>> WinMsiBundler to create more "-ext XYZExtension" options).  But even
>>> just having the UI extension hardcoded inthere would get it to work.
>>>
>>> I can probably just do the change locally and install a custom version
>>> of the JFX stuff in my repository, but I think it would be a worthwhile
>>> change to the repo overall.
>>>
>>> Thanks!
>>>
>>> Scott Lewis