JDK-8273593 : [REDO] Warn user when using mac-sign option with unsigned app-image.
  • Type: Bug
  • Component: tools
  • Sub-Component: jpackage
  • Affected Version: 16,17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • Submitted: 2021-09-10
  • Updated: 2025-02-03
  • Resolved: 2021-09-14
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 17
17.0.2 b01Fixed
Related Reports
Blocks :  
JDK-8273592 - Backout JDK-8271868
Cloners :  
JDK-8271868 - Warn user when using mac-sign option with unsigned app-image.
Relates :  
JDK-8286850 - [macos] Add support for signing user provided app image
Relates :  
JDK-8271868 - Warn user when using mac-sign option with unsigned app-image.
Description
When jpackage is building a dmg or pkg bundle in two phases (that is, building an app-image type first and then using that app-image to build dmg or pkg bundle), and if signing is used, the --mac-sign option may be needed in both phases.
Though not strictly an error (you can build a signed pkg containing an unsigned app-image, or an unsigned pkg containing a signed app-image) the result could not be notarized, as both package and app-image needs to be signed to pass notarization.

We have had at least one user wondering why notarization failed in such a case, So this issue proposes to add a warning message when an unsigned app-image is used to build a bundle using --mac-sign option.
Comments
Changeset: ec0b85ab Author: Andy Herrick <herrick@openjdk.org> Date: 2021-09-14 18:11:12 +0000 URL: https://git.openjdk.java.net/jdk17u/commit/ec0b85ab5fd4cee7586911ab4f3448469b171bbb
14-09-2021
Now that the original fix for JDK-8271868 is backed out by JDK-8273592, and synced into jdk17u, it can be redone in jdk17u (not jdk17) for 17.0.2 using this bug ID. NOTE: It does not need to be redone in mainline jdk for JDK 18, since the original fix is still present and actual there.
10-09-2021