JFX build and deployment - squeaking wheel

Scott Palmer swpalmer at gmail.com
Sat Nov 3 11:07:15 PDT 2012

Right. MSI is sort of an official MicroSoft Installer format.  The .msi file is read by the built-in Windows installer APIs. Sort of like how .pkg is handled natively by OS X, and .rpm and .deb are handled natively by Linux distros.  Exe installers could be anything, they just aren't the same. though often they are special bootstrappers tacked on to one or more MSI databases. MSI is a table-based description of the stuff to install. (It isn't particularly good mind you, it's just well supported by the Windows OS.)


On 2012-11-03, at 12:10 PM, Joshua Marinacci <joshua at marinacci.org> wrote:

> Ah. So an MSI is not just another installer format? It has special
> properties make it different than NSIS?
> Most likely sent from Planet Earth
> On Nov 3, 2012, at 6:45 AM, Richard Bair <richard.bair at oracle.com> wrote:
>>> I just tried using the AppBundler (the other one from Java.net) to create a Mac bundle with an embedded JRE and it worked pretty well.  For Windows is an MSI file a requirement or could some other installer system work? I just found NSIS which can generate Windows installers from linux.
>> The reason MSI is important is that for many large sites with IT departments, they don't want to have to go around from machine to machine manually installing software and, they don't trust users to be able to download and install software themselves (either by policy or by some means of enforcement). Giving the IT department an MSI allows them to remotely push updates / software onto the correct users machines according to whatever policies they've crafted in their business. Or remove the software when the time comes.
>> Richard

More information about the openjfx-dev mailing list