Build Options / Advanced Interface

Build Options

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

If a JVM file isn't installed: If any of the installers that can include the JVM are grayed out, then follow these instructions.

JExpress performs only the functions with a check mark next to them when you click the Build button. 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
Subproject
Build directory
Erase all of the Build directory before using
Installers: Windows Solaris Linux Pure Java
Distribute to web or ftp site
Build

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.

Project Type

If you want to create installers and updaters, then select the Installers radio button. This is the default selection and allows you to define which type of installers you want for this project and whether you want JExpress to upload your installers and updater online.

If you'd like JExpress to layout your files in a directory tree, but not build an installer for those files, then select Subproject. Creating a subproject allows you to find classes for a program and then include those files in your installer project.

Subprojects are very useful when you have custom classes for JExpress. You can create a subproject that finds all the classes your custom classes use and then include the build directory of the subproject in the appropriate Custom directory.

If you simply want to jar your application, with a full manifest, then select Jar only. If you create a Jar only project that also find classes automatically the Jar file's manifest will include the "Main-class" specification.

Whenever you select Subproject or Jar only you won't be able to select the type of installer or be able to upload the build directory's content online. JExpress builds the subproject and jar file locally on your system and then you can simply include the build directory in the installer project.

Be sure to build subprojects and jar only projects before you build the installer project. To learn more about building subprojects, review the tips on Multiple Related Projects or follow the step-by-step instructions.

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.

Installers

Add a check mark to the checkboxes that indicate which types of installers you want created for your application. 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 Custom Native license and adapt the native installer to your environment. You must have purchased at least one license to JExpress for each JExpress Custom Native license you purchase.

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 correct 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.

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 correct 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.

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 correct 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.

Pure Java:

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

Distribute to web or ftp site

If you'd like JExpress to upload your distribution files to your web or ftp site, then check this box. You must have entered all the information on the Distribution panel for JExpress to upload your files.

We recommend that you leave this field blank until you are successfully building your project. You might even want to test your installer offline before you add a check mark to this field to distribute it.

If you don't have any of the installer check boxes checked, and you do have this distribute box checked, then JExpress will simply verify that it's ready to build, and then upload all the files and subdirectories you have in your build directory to your ftp site.

Build

When you click this button, JExpress saves your project and then performs all the tasks you selected. If you checked Distribute, be sure your machine is connected to your web or ftp site.

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.

JVM | Custom | Groups | Distribution | Messages