A project is saved to a single XML file with an.install4j extension. If you feel that there's a lack of documentation in a certain area or if you find inaccuracies in the documentation, please don't hesitate to contact us at 4ĥ A Concepts A.1 Projects Overview Project files A project in install4j is the collection of all information required to build media files. The sections at the end are optional readings that should be consulted if you need certain features. How do I continue? The "Concepts" section is intended to be read in sequence, with later help topics building on the content of previous ones. Building installers is not only possible in the IDE, but also with the command line compiler as well as the plugins for Gradle, Maven and Ant. The install4j UI is delivered as a desktop application. JRE bundles can also be downloaded on the fly if no JRE installation is found. Bundling of Java Runtime Environments Bundling a Java runtime is made easy with the pre-build JRE bundles and the bundle creation tools in install4j. Update downloaders are fully configurable installer applications with their own flow of screens and actions, that can handles interactive auto-update, mandatory auto-update at startup and background update. Auto-update functionality The requirements for automatic updates are very individual, so install4j offers a template-base mechanism for update-downloaders. At runtime, there is launcher API that interacts with some of these feature and with the variable system of the installer. These launchers offer variety of features such as flexible module and classpath configuration, version-specific VM parameters, icons, splash screens and much more. Generation of native launchers install4j generates native launchers for console, GUI and service executables. A rich set of configurable actions handles a variety of tasks and is extensible with the API. Configurable form screens allow you to create arbitrary forms that work in GUI and console mode. Main features that distinguish install4j are: Flexible configuration of screens and actions In your installers you can define your own flow of installer screens and installer actions to gather user input and initialize your installation with it. 5 A.2 Building projects A.3 Distributing files A.4 File sets and components A.5 Screens and actions A.6 Scripts A.7 Generated launchers A.8 Form screens A.9 Layout groups A.10 Styles A.11 Variables A.12 Localization A.13 VM parameters A.14 JRE bundles A.15 Services A.16 Elevation of privileges A.17 Merged projects A.18 Auto-update functionality A.19 Version numbers A.20 Media files A.21 Data files A.22 Code signing A.23 Styling of DMGs on macos B Configuring installer beans B.1 Screens & actions step B.2 Custom code B.3 Configuring applications B.4 Configuring screens B.5 Configuring actions B.6 Configuring groups B.7 Configuring form components B.8 Configuring layout groups B.9 Configuring styles C Generated installersģ C.1 Installer modes C.2 Command line options C.3 Response files C.4 JRE search C.5 HTTP requests C.6 Updates C.7 Error handling D API D.1 Installer API D.2 Launcher API D.3 Extensions E Command line tools E.1 Command line compiler E.2 Gradle plugin E.3 Maven plugin E.4 Ant task E.5 Pre-Created JRE BundlesĤ Introduction To Install4j What is install4j? install4j is a professional tool for building installers for multiple platforms, especially for applications that run on the Java Virtual Machine. All rights reserved.Ģ Index Introduction. 1 The definitive guide to install4j Building professional installers on the JVM 2019 ej-technologies GmbH.
0 Comments
Leave a Reply. |