Building from Source

After retrieving the source code the build can be done with Maven as easy as calling:

After the build has finished successfully, the KickStar executable jar can be found in target directory.

Installation

The Installation can be done anywhere wanted. On Unix like System an installation directory like /opt/JavaApp is suitable. Within this directory place the kickstart.jar and the KickStart.properties file (beware of small and capital letters in Unix OS). Additionally, some directories need to be added to place the actual libraries into it. A recommendation is to create the following sub-directories:

• bin: Within this directory all executable scripts are located which actually start KickStart and choose the Class in which the needed main() method can be found for startup.
• config: This directory should be treated as class library directory and is used for configuration files which are placed into the CLASSPATH and loaded as resource.
• extlib: To extlib all libraries from external vendors should go in.
• lib: Should be the directory where all classes go in which are from own developments and which are changed during development cycles.
• log: Within this directory all log files which are generated by the tools should be located. KickStart itself does not generate any log files.

All directory naming is meant to be inside the installation directory of the KickStart framework.

Starting an Application

After a successful installation of KickStart and the needed libraries, KickStart can be started a normal JRE as easy as:

The version information needs to be adapted. MainClassName is to be replaced with the actual main class containing the main method for startup. The parameters for the application follow afterwards as usual.

Additional System Configuration

In the next sections some information is given beyond the normal KickStart setup to include the Java application more deeply into the OS.