...
- The initial Installer is packaged using One-Jar. One-Jar essentially provides us with an easy way to create an executable JAR file.
- When a user runs the JAR file, the One-JAR 'Boot' class is automatically called
Wiki Markup The One-JAR 'Boot' class automatically calls whatever is located at {{/main/main.jar}} within the installer.jar file. In our case, {{/main/main.jar}} calls the new dspace-install-api.jar file (see {{\[installer-prototype\]/dspace/src/assemble/installer-assembly.xml}} for details)
- The dspace-install-api.jar is what actually performs the installation
Wiki Markup NOTE: The 'dspace-installer.jar' actually includes a full copy of all third party dependencies (JARs) as well as a copy of the DSpace install directory. See the {{\[installer-prototype\]/dspace/src/assemble/installer-assembly.xml}} for details.
Overview of dspace-install-api
The heart of this Installer is the new /dspace/dspace-install-api/ module. This module currently only includes a few new files:
Wiki Markup {{org.dspace.install.Installer}} - This is the main executable Installer class. Currently, it essentially just uses the Apache Ant API to call a custom Installer 'build.xml' file (which is based off the default DSpace {{\[installer-prototype\]/dspace/src/main/config/build.xml}} file). NOTE: Even though this installer uses the Ant API, Ant is *not* required to be installed on the local system. The Ant API is included within the Installer itself.
/src/main/resources/installer-build.xml- This is the Ant Build file which actually tells Ant what it needs to do to actually perform the Install process.