Comments on jpackage (JEP 343)

Alexey Semenyuk alexey.semenyuk at
Wed Sep 25 23:58:26 UTC 2019


Thank you for your feedback. I've captured it in

- Alexey

On 9/25/2019 9:45 AM, Sverre Moe wrote:
> I have some new comments regarding the Windows build of jpackage.
> 1)
> Is there any way to build an trusted application installer using WiX?
> I want to avoid "Unknown Publisher" when installing the application.
> Also having problems with Windows Defender SmartScreen, depending on what
> settings the user has (Block, Warn, Off).
> If Block, the user cannot install the application. If Warn, the user can
> click "More info", then "Run anyway".
> 2)
> The EXE installer details has no information about the actual application
> it will install.
> File version: 14.0.0
> Product Name OpenJDK Platform 14
> Product version: 14
> This is not quite right, since the application was built with Java 11, only
> packaged with jpackage from Java 14.
> Should it not use the name and app version supplied to jpackage on these
> properties.
> Original filename: msiwrapper.msi.
> It should be the name supplied to jpackage used here at least >
> applicationName.msi
> Building an MSI has much better detail properties, but a couple of the
> description properties says nothing about the actual application.
> Title: Installation Database
> Comments: This installer database contains the logic and data required to
> install applicationName.
> Any way to change the title and comments?
> 3)
> The icon for the installer file is not using the one from the resource
> directory. If supplied the --icon argument is not used.
> Both Explorer and List of installed application shows a generic application
> icon.
> 4)
> MSI installer has a Category detail property. Perhaps jpackage should have
> an --windows-category argument.
> 5)
> Help text for --icon argument should mention that it needs to be an ICO
> when packaging on Windows.
> Currently there is no way to supply a custom WXS file to WiX in the
> resource directory. Perhaps this could help further customization.
> /Sverre
> tor. 19. sep. 2019 kl. 20:29 skrev Kevin Rushforth <
> kevin.rushforth at>:
>> OK, that makes sense. Andy has already implemented this change (pushed
>> it to the sandbox), so it will be in the next EA build.
>> -- Kevin
>> On 9/19/2019 10:25 AM, mark.reinhold at wrote:
>>> jlink’s -o/--output option names exactly the thing being output,
>>> rather than a container for the thing being output.
>>> The jpackage option we’re discussing here names a container for the
>>> thing being output, much like the -d option of javac and javadoc.
>>> Using -d/--dest for jpackage is consistent with the JDK’s other
>>> command-line tools.
>>> - Mark

More information about the core-libs-dev mailing list