Introduction
This guide details the process for installing the Direct Certificate Discovery Tool (DCDT, or the Tool) from a version of the source code. If you do not have a need to build the source code, then please skip this guide and use the prebuilt Linux package as described in the package installation guide.
Requirements
See the System Requirements Install Guide for instructions on how to prepare your system prior to installation of the Tool.
The following steps are to check out the release tag and build the source code.
Checkout the Sources
Use the Mercurial CLI to checkout the desired version.
To clone the repository and checkout the tip (newest revision of the default branch), run the following:
hg clone https://code.google.com/p/direct-certificate-discovery-tool/ ~/direct-certificate-discovery-tool
Typically, the latest stable release tag should be used for deployments. To checkout this tag, run the following:
cd ~/direct-certificate-discovery-tool
hg update dcdt-2.1.2-RELEASE
Build the Projects and Assemblies
To build all of the Maven projects that comprise the Tool and generate assemblies, run the following:
cd ~/direct-certificate-discovery-tool/assembly
mvn clean install
Developer Functionality
The following sections describe advanced functionality typically reserved for developers.
Checkout the Sources for Development
To checkout the trunk for development (project membership required), the tip needs to be checked out by running the following:
hg clone https://code.google.com/p/direct-certificate-discovery-tool/ ~/direct-certificate-discovery-tool
Upon pushing, you will be prompted to enter your password. This is not your Google account password, but a string that Google Code has generated for you. It can be retrieved from your Google Code profile.
Build Individual Projects
It is possible to build the Maven projects that comprise the Tool without generating assemblies. To do so, run the following while in a directory other than ~/direct-certificate-discovery-tool/assembly:
mvn clean install
An aggregate Maven project exists in the parent directory of all of the Maven modules (direct-cert-discovery-all).
Running the previously mentioned command while in this directory will build all of the modules. In order to build individual modules, simply change your current directory to that of the module.
Note: Except for direct-cert-discovery-all and direct-cert-discovery-assembly, all other modules require that any dependency modules specific to the Tool are installed in the local Maven repository prior to the start of the build. Thus, it is usually preferable to build using the direct-cert-discovery-all module, as it will apply any goals recursively.