P2 Description
Many of the jpackage options that are specifically for create-installer mode on windows and unix are used in create-image mode on mac.
Before EA 4 (build 30) such options generated a warning, but were used anyway. Now they are an error (when used in create-image mode).
This may have been masked before by the problems we had using --app-image on MAC. Because of those bugs, you could not really run "jpackager create-image" followed by "jpackager create-installer --app-image" and build your app in two separate steps on MAC.
Now that you can, options such as "--associations" which are listed as a "create installer" option, cannot be used in the first step, where they are needed in the first step on mac.
The point is the Info.plist generated for by Mac MacAppImageBuilder contains the directives that are part of the installer on other platforms.
We need to look at each option currently listed as installer mode option and make sure if it is used by MacAppImageBuilder then it should be allowed in create-image mode (at least on MAC).
Before EA 4 (build 30) such options generated a warning, but were used anyway. Now they are an error (when used in create-image mode).
This may have been masked before by the problems we had using --app-image on MAC. Because of those bugs, you could not really run "jpackager create-image" followed by "jpackager create-installer --app-image" and build your app in two separate steps on MAC.
Now that you can, options such as "--associations" which are listed as a "create installer" option, cannot be used in the first step, where they are needed in the first step on mac.
The point is the Info.plist generated for by Mac MacAppImageBuilder contains the directives that are part of the installer on other platforms.
We need to look at each option currently listed as installer mode option and make sure if it is used by MacAppImageBuilder then it should be allowed in create-image mode (at least on MAC).