Check Out and Compile
We use maven version 2.0.4 for building Triplesec server. To download and install maven please see the maven site and documentation here. Below you'll find a sequence of commands issued to checkout and build triplesec server. (Even if the code has recently been moved to apache the previous releases can still be found at the former location of the TripleSec project)
svn co https://svn.safehaus.org/repos/triplesec/releases/0.7 triplesec-0.7 cd triplesec-0.7 mvn install
If you want to work on the bleeding edge you can checkout and build the trunk instead. To do so simply substitute the checkout URL for subversion to:
svn co http://svn.apache.org/repos/asf/directory/triplesec/trunk-with-dependencies/ triplesec-trunk
Building Installers
Building the installer is easy. To kick off the build just cd into the installers directory in the triplesec project root and issue the following command:
mvn clean install
Make sure to issue the clean as well as the install command to maven. The first time it might work without clean but the second time you try to build the installers it will fail without the clean command.
Types of Installers
There are 3 types of installers that are generated by the installers module. A win32 executable, Java based GUI installers using Izpack, and an RPM installer for Linux. Several Izpack installers are generated for various UNIX platforms and MacOSX.
Some installers like the RPM installer and the Win32 executable installer based on Inno Setup have some requirements. These installers will not be generated when building the installers unless these requirements are met.
Windows Executable Installer (Inno Setup) Requirements
The Inno Setup installer will only be generated when building on Windows platforms. This is because the installer compiler for Inno is only available on Windows. Furthermore the Inno Setup tool must be installed on your system. Download the Inno Setup QuickStart pack here and install it in the default location. If you do not install it in the default location please make sure it's on the path so maven can see it.
RPM Installer Requirements
First off you have to be on a system with RPM installed. Although people have RPM installed on platforms like Solaris this will probably only work for Linux at this point and more specificially on RedHat platforms.
The installer plugin that builds all these installers will assemble the directory layout for building the RPM but will abort the generation of the RPM if you're not building the installers as the root user. This is because you don't have access to the directories that the RPM is deposited into. So building the installers as root will make sure the RPM is generated. Again the same simple 'mvn clean install' command is used.