# Building the OCL Project

This section contains some details on the way in which the OCL project is built. This should only be of interest to users creating extension of the project.

The interactive build facilities may be found in the org.eclipse.ocl.examples.build plugin. The “Generate OCL All” launch invokes all the sub-generators for models and editors.

The documentation build uses the “OCL Documentation” Ant external launch; see org.eclipse.ocl.doc/libs/Readme.txt for prerequisites. The build populates the help/html/manual folders whose content should be committted to GIT to ensure that the regular build uses the updated documentation. Publishing ocl.pdf is an option that can be selected when performing a final Jenkins reklease build.

The Javadoc build uses the “Run OCL Javadoc using Ant directly” Ant external launch. The build populates the javadoc folder which should not be committted to GIT. Generating and publishing the javadoc is an option that can be selected when performing a final Jenkins release build.

The distribution build facilities uses the Maven pom.xml in the org.eclipse.ocl.releng.tycho plugin. The “Build OCL Distribution - Nightly” replicates the Jenkins build locally differing only the absence of the final signing. The build populates the org.eclipse.ocl.releng.build-site plugin

## OOMPH

There is an org.eclipse.ocl.oomph/setups/ocl.setup that users may find helpful to create a development workspace, but the setup is not used by the developers and so may be stale.