In this page you can specify the settings for the Mac OS X package.
For a Mac OS X bundle to be created you must create a Mac OS X Build in the Media page.
Not all the features of a MSI package are available for a Mac OS X package. There are supported only Multiple Java Products, File Associations and most of Java settings (splash screen, JVM type and Library path are not supported). Other settings like custom actions, environment variables, registry etc. are not supported as they are specific to Windows platforms.
Include the Java Product in the Mac OS build
This option allows you to choose whether the product will be added or not to the Mac OS build.
Files and Folders
This section allows you to add resources to the Mac OS X package.
The tree control is divided into two sections:
- Product Section - Contains the files that will be deployed in the current product's Java directory.
- Common Section - Contains the files that will be deployed in the Mac OS X product's root folder. This section is the same for all java products.
If you are deploying several products you can share files between the products, to reduce the archive's size. Only the files whose location is included in the classpath list can be shared.
When a product needs a JAR or a folder that is not found in the classpath it will search for it in it's Resource folder. If it doesn't find it, it will try to search for it in the root folder. If this fails, it will search for it in the other products Resource folders.
Adding a folder
Use thebutton or “Add Folder...” context menu option.
Use thebutton or “Add Files...” context menu option.
Removing files or folders
Use the Delete key while an element from the tree is selected.button, the “Remove” list context menu item or press the
Copying files and folders between sections
Drag and drop resources between sections while the Shift key is pressed or use the “Copy to Product Section/Copy to Common Section” context menu options.
Moving files and folders between sections
Drag and drop resources between sections or use the “Move to Product Section/Move to Common Section” context menu options.
The resources must be dropped over the other section's root item.
When copying or moving resources between components they will be added with their full path.
For more details on how to localize a Mac OS X package please go to Java Product Localization page.
This the version that presented to the user into the application about panel, but is not interpreted by the system. If no value is specified in this field then the java product name and the package version will be used instead. This field is of PseudoFormatted Type and can be edited with Smart Edit Control.
Required OS X Version
This is the minimum required OS version for your application.
If you specify a version higher than the one the bundle is deployed on, the application will not work.
This field identifies the file containing the icon for the bundle. The icon file will be looked up in the Resources directory of the bundle.
The value for this field is a string containing a four-letter code which is specific to the bundle. For example, the signature for the TextEdit application is txt.
This is a unique identifier string for the bundle. This identifier should be in the form of a Java-style package name, for example com.mycompany.myapp. The bundle identifier can be used to locate the bundle at run-time. The preferences system also uses this string to uniquely identify applications. This field is of PseudoFormatted Type and can be edited with Smart Edit Control.
No Dock icon and no Menu Bar interaction
This option specifies that the application will run as an agent. Agent applications are not displayed in the Dock, in the Force Quit window or in the Menu Bar. Usually they are background applications but they can come to the foreground to present a user interface if desired.