None of these fields are required. Defaults work fine in most cases. But if you'd like to tweak the packaging process, here's your opportunity.
Choose where you'd like to move the resulting package. The default location is the same place where the Jar Ajar pacakger resides. Note that this field has nothing to do with where your users choose as the final destinations of their extracted package contents.
Example: C:\builds
.
Type a command that you would like executed after your package has been installed on the user's system. The command should be given just as if it were typed on a command-line, and files should be relative to the directory in which the package was installed. The java
command will automatically locate and use the same Java binaries that are running Jar Ajar. The user will have the option of running this command, and if none is provided, no option will be offered.
Example: java -jar installdir/MyProgram.jar
Display a readme of your choice once the extraction is completed. Provide a file relative to the directory in which the package was installed. The user will have the option of running this command, and if none is provided, no option will be offered.
Example: installdir/readme.txt
You can included a license that the user must agree to before installed your package. This file will be packaged separately from your zip file and does not depend on any contents in it.
Example: /home/susan/License.txt
.
(Optional) Specify the default location where your package will be installed. If the directly exists, it will be pre-selected for installation, and if not, an attempt will be made to create it. "user.home" can also be used to specify the user's home directory, or "user.dir" for the current directory, and the path can be further built relative to these directories. By default, the current working directory will be used.
Example: user.home/myapp
.
If checked, the self-extractor will attempt to install the package immediately upon launch, without even displaying a window. This option can be used in conjunction with the Default Install Directory path and Run Application option to deploy an application to a specific directory before launching the app or an updater.