It is very convenient to use install4j to make installation packages for java programs.
Generic Settings: Configure the project and company information, the naming and compression method of the installation package, etc.
Files: The resources and library files that need to be packaged and released are generally generated in the same directory (such as target/build), and then the required files are added. You can also define components (a collection of different files) for users to choose and install.
Launchers: You can reference externally generated executable files (such as exe files generated by launch4j), but install4j also supports generating executable files, and can configure startup types (command line, interactive interface, system services), file attribute information, and file icons , main class and virtual machine parameters, classpath and splash screen. When the main class is specified, install4j will automatically search the class path. In order to reduce the size of the installation package, the jar file can be compressed by pack200. When the main class is started, these files need to be automatically decompressed and the class path is dynamically updated. When configuring virtual machine parameters, if the value of a parameter contains spaces, the entire parameter should be enclosed in quotation marks, such as "-Dappdir=C:/Program Files/app", but do not mix quotation marks with other parameters, such as -Xms20m - Xmx120m. The generated executable file is used to create shortcuts in the start program menu, quick launch bar and desktop, which become the entry for program startup.
Installer: Configure the installation interface and actions. Generally, it is enough to choose from the standard. Common actions include adding shortcuts and deleting program directories during uninstallation.
Media: Installation package file definition, specifying the applicable platform, whether to bind jre, files to be excluded, etc. If there is no jre, it is best to dynamically bind to a tar.gz package on the network, so that if the jre is missing during installation, it will prompt to locate an existing jre, or download the jre on the network. And the bound jre installation is shared, avoiding repeated download or maintenance of multiple jre.
Build: Build the installation package.