JDK-8275073 : Allow additional msi installers in jpackage exe build
  • Type: Enhancement
  • Component: tools
  • Sub-Component: jpackage
  • Affected Version: 17,18
  • Priority: P4
  • Status: In Progress
  • Resolution: Unresolved
  • OS: windows
  • CPU: x86
  • Submitted: 2021-10-11
  • Updated: 2024-08-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25Unresolved
Related Reports
Relates :  
Relates :  
Description
When building an exe image for a jpackaged application we first create an msi, then create a wrapped exe that invokes it.

It could be useful to allow including other msi installers to be co-bundled with the jpackage app.
Comments
originally part of https://bugs.openjdk.java.net/browse/JDK-8208405, now extracted as an independent enhancement. The syntax for the new cli: --win-co-bundles <path to additional msi bundle>[,<path to additional msi bundle>...] A a comma separated list of paths to msi installers to be included in the bundle. This option is valid only when the target type is "exe". The win-co-bundles must be paths to existing msi installer(s). The windows msi exe wrapper will include the msi for the co-bundles, and the msi for the app, and all will be executed when the exe bundle is executed. The desired behavior is for the co-bundled msi to run silently, and do nothing if either it or a later update of it is already installed. This currently is not the default behavior of the full JDK msi bundles provided by Oracle, but is the default behavior of a java runtime bundle packaged by jpackage.
11-10-2021