-
Bug
-
Resolution: Fixed
-
P4
-
16, 17, 18
-
b01
-
os_x
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.
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.
- clones
-
-
- Resolved
-
- is blocked by
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
JDK-8286850 [macos] Add support for signing user provided app image
-
- Resolved
-
(1 links to)