|
|
|
After you've set all the options in the other panels, then use the Build panel to create your installers, and optionally autoupdaters.
If a JVM file isn't installed: If any of the installers that can include the JVM are grayed out, then follow these instructions.
If there are any errors during the Build, look up each error number for suggestions and work arounds. After JExpress builds your installer, learn more about testing your system and the location of your distribution files. Click on the jump point or just page down to learn more about each setting on this panel.
Version
Build directory
JExpress defaults the Build directory to a subdirectory in your JExpress directory that matches your project's name. You can leave this field blank if you want to use the default, and JExpress will name and create the directory when you name the project.
Learn more about where JExpress stores your distribution files after it builds your installer.
Erase all of the Build directory before using
IMPORTANT: If you check this box, then JExpress will delete all subdirectories. On Unix, be very careful about linking to other directories to the Build directory. For example, if you'd link the root to the Build directory and then check this field, JExpress could delete all files on the drive.
IMPORTANT: Regardless if this box is checked or not, JExpress deletes the standard subdirectories created under the Build directory (e.g., installers, howto).
Installers
If JExpress doesn't currently support a native installer for one of your desired platforms, then you can purchase a JExpress Installer Source license and adapt the native installer to your environment.
When you add a check mark to the Windows checkbox that includes the JVM, then an EXE file is created which automatically detects whether the JVM is on your customers' systems, installs it if it is not, and then installs your application.
If you add a check mark to the Windows checkbox with no JVM, then an EXE file is created which verifies that the correct JVM is installed on your customers' systems, but only reports to the user if it isn't. If the installer finds the correct version of the JVM, then it proceeds to install your application.
Apple does not allow you to distribute the JVM, but all Mac OS's since 10.2 include the JVM.
If you add a check mark to the Mac checkbox with no JVM, then a gzip file is created which includes the Mac application inside. Your customers simply double click on the gzip file and if they don't have StuffIt configured to launch the app inside, they simply click on the icon to start the installer.
If you prefer to distribute a DMG file and you create your installers on a Mac and you create your installers as an administrator, then you can create an ant target which takes the following steps after JExpress creates the Mac native installer.
When you add a check mark to the Linux checkbox that includes the JVM, then a binary file is created which automatically detects whether the JVM is on your customers' systems, installs it if it is not, and then installs your application.
If you add a check mark to the Linux checkbox with no JVM, then a binary file is created which verifies that the correct JVM is installed on your customers' systems, but only reports to the user if it isn't. If the installer finds the correct version of the JVM, then it proceeds to install your application.
When you add a check mark to the Solaris checkbox that includes the JVM, then a binary file is created which automatically detects whether the JVM is on your customers' systems, installs it if it is not, and then installs your application.
If you add a check mark to the Solaris checkbox with no JVM, then a binary file is created which verifies that the correct JVM is installed on your customers' systems, but only reports to the user if it isn't. If the installer finds the correct version of the JVM, then it proceeds to install your application.
Build
If there are any errors during the Build, look up each error number for suggestions and work arounds. After JExpress builds your installer, learn more about testing your system and the location of your distribution files.