- -h or --help
Displays a quick help for all available options.
- -V or --version
Displays the version of install4j in the following format:
install4j version 2.0, built on 2003-10-15
- -v or --verbose
Enables verbose mode. In verbose mode, install4j prints out information about
internal processes. If you experience problems with install4j, please make sure
to include the verbose terminal output with your bug report.
- -q or --quiet
Enables quiet mode. In quiet mode, no terminal output short of a fatal error
will be printed.
- -t or --test
Enables test mode. In test mode, no media files will be generated in the media
file directory.
- -i or --incremental
Enables incremental test execution. A test installer for the current platform
is updated with the latest screens, actions and form components and executed immediately.
Because the files are taken
from a previously built media file, the compilation is very fast.
- -g or --debug
Create additional debug installers for each media file. For each built media file,
a directory that is named like the media
file will be created in the media file output directory.
- -n or --faster
Disable LZMA and Pack200 compression. If you have enabled LZMA or Pack200 compression
on the
media file options tab,
this allows you to create development builds much faster, since LZMA and Pack200 are
expensive compression algorithms.
- -u or --disable-signing
Disable code signing. If you have configured
code signing,
this allows you to skip code signing for a build. In that case you do not have to
enter the passwords for the key stores.
- -j or --disable-bundling
Disable JRE bundling. If you have configured
JRE bundles for any media files, those bundles will not be used and
the installer will be built without a contained JRE. This speeds up the build and
the installation.
- --win-keystore-password
Set the Windows keystore password for the private key that is configured for
code signing. If code signing is enabled for Windows media files
and this option is not set, the command line compiler will prompt you for the password.
- --mac-keystore-password
Set the Mac OS X keystore password for the private key that is configured for
code signing. If code signing is enabled for Mac OS X media files
and this option is not set, the command line compiler will prompt you for the password.
- -L or --license=KEY
Update the license key on the command line and exit. This is useful if you have installed
install4j on a headless system and cannot start the GUI.
KEY must be replaced with your license key. If you use floating licenses,
replace KEY with FLOAT:server where "server" is the host name or IP address
where the floating license server is installed. For floating licenses, you can choose
the requested edition
by passing --windows-edition or --multi-platform-edition.
- -r STRING or --release=STRING
Override the application version defined in the
General Settings step.
STRING must be replaced with the desired version number.
Version number components can be alphanumeric and should be separated by dots, dashes
or underscores.
- -d STRING or --destination=STRING
Override the output directory for the generated media files. STRING must
be replaced with the desired directory. If the directory contains spaces, you must
enclose STRING in quotation marks.
- -s or --build-selected
Only build the media files which have been selected in the install4j IDE.
By default, all media files are built regardless of the selection in the
Build step.
- -b LIST or --build-ids=LIST
Only build the media files with the specified IDs. LIST must
be replaced with a comma separated list of numeric IDs. The IDs for media files
can be shown in the install4j IDE by choosing Project->Show IDs
from the main menu. Examples would be:
-b 2,5,9
--build-ids=2,5,9
- -m or --media-types=T[,T]
Only build media files of the specified type. T must
be replaced with a media file type recognized by install4j. To see the list of supported
media
types, execute install4jc --list-media-types.
Examples would be:
-m win32,macos,macosFolder
--media-types=win32,macos,macosFolder
- -D NAME=VALUE[,NAME=VALUE]
Override a compiler variable with
a different value. You can override multiple variables by specifying
a comma separated list of name value pairs. NAME must be the
name of a variable that has been defined on the
Compiler Variables tab of the
General Settings step. The value
can be empty.
To override a variable for a specific media file definition only, you can
prefix NAME with ID: to specify the ID of the
media file. The IDs for media files can be shown in the install4j IDE by choosing
Project->Show IDs from the main menu.
Examples would be:
-D MYVARIABLE=15,OTHERVARIABLE=
"-D MYVARIABLE=15,OTHERVARIABLE=test,8:MEDIASETTITLE=my title"
A special system variable that you can override from the command line is
sys.languageId. sys.languageId must be set to the
ISO code of the language displayed in the
Language selection dialog
and determines the principal installer language
for the project or the media file.
- -f or --var-file
Load variable definitions from a file. This option can be used together with the
-D option, which takes precedence if a variable occurs twice.
The file can contain
- variable definitions
One variable definition per line of the form NAME=VALUE.
- blank lines
blank lines will be ignored.
- comments
lines that start with # will be ignored.
The file is assumed to be encoded in the UTF-8 format.
Should you require a different encoding you can prefix the filename with
CHARSET:, where CHARSET is replaced with the name of the encoding.
Instead of a single variable file you can also specify a list of files separated by
semicolons. The optional charset prefix must be specified for each file separately.
Examples would be:
-f varfile.txt
--var-file=ISO-8859-3:varfile.txt
--var-file=one.txt;two.txt
--var-file=ISO-8859-3:one.txt;ISO-8859-1:two.txt
- -M or --list-media-types
Prints out a lists of supported media types for the --media-types
option and quits.