Build Options

After you've set all the options in the other panels, then use the Build panel to create your installers, and optionally autoupdaters.

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

Specify the current version number or method of distinguishing this release from previous releases. This information displays on your install program's splash screen.

 


 

Add test icons

Include a check mark if you want icons added to the desktop after you build your installers. This makes it easy to test the installer on the computer where you created it.

You also have the option of using the Test button from inside JExpress. Of course, if you want to test an installer for a different OS than the computer you're using, you'll need to move the installer to that computer.

 


 

Build directory

The Build directory is where JExpress prepares your files for distribution. We recommend that this directory be a new directory so JExpress doesn't interfere with other files on your system.

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

Check this box if you'd like JExpress to erase all the files in the Build directory and its subdirectories before JExpress creates a new distribution.

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

Add a check mark to all of the checkboxes to indicate which types of installers you want created for your application. JExpress can create installers that either include the JVM or don't. JExpress can create installers that include the JVM or not. We do not usually include all the JVM files so we suggest that you follow these instructions before you try to build.

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.

Windows:

Add a check mark next to the Windows checkbox(es) if you want to build an executable file that installs your application.

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.

Mac:

Add a check mark next to the Mac checkbox if you want to build a Mac bundle that installs your application.

Remember that if you want to distribute Java 7 or later on Mac, then it can only be installed on OS X 10.7.3 or later. Also, the installer always installs the JRE on Mac in a subdirectory of the installation directory, called .jre.

If you add a check mark to the Mac checkboxes, then a DMG is created if you're running JExpress Builder on OS X or Linux (Linux requires genisoimage be installed in the path). Otherwise, a gzip file is created which includes the Mac application inside. Either way, your customers simply double click on the distribution file and then simply click on the icon to start the installer.

If you'd like to create a DMG installer for Mac on Windows, then you might be able to use a 3rd party commercial product. Simply create a batch file called mkdmg-on-windows.bat which invokes the 3rd party program and accepts the volume name, app bundle directory to be compressed, and the total size of the DMG in megabytes on the command line. Put the batch file in the macapp subdirectory of the JExpress directory. If JExpress cannot create a DMG when the batch file is executed during the build, then it creates a tar.gz file instead.

Linux:

Add a check mark next to the Linux checkbox(es) if you want to build an binary file that installs your application.

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.

Solaris:

Add a check mark next to the Solaris checkbox(es) if you want to build an binary file that installs 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.

Cross Platform:

Check this box if you want to create a Cross Platform installer. The Cross Platform installer is more compact than the native installers because it doesn't include the JVM. It also works behind firewalls that don't allow executables, by providing a single JAR file that your customers download and load. Your customer must have the JVM already installed before they can use the pure Java installer.

Java Web Start:

If you want to create a Java Web Start installer, start JExpress with Advanced interface.

 


 

Build

When you click this button, JExpress saves your project and then builds your installers, and optionally prepares the updates files.

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.