loading table of contents...

3.5.1. Building the Workspace

The CoreMedia Blueprint workspace contains a complete CoreMedia CMS system. The first step is to build the system and to start all components or boxes. This enables you to test your changes and new features locally, which is a convenient setup for a new project.

In this manual $CM8_BLUEPRINT_HOME will refer to the root directory of the Blueprint workspace. If you set it as an environment variable, you can simply copy and paste the command line snippets. Otherwise, you have to substitute paths accordingly.

Go to the Blueprint workspace and build the system with the following commands:

$ cd $CM_BLUEPRINT_HOME
$ mvn clean install

If you want to build without tests, add the -DskipTests option to the Maven call.

[Note]Note

If you want to prepare your build environment to be independent of any network resources, you can achieve this by calling mvn dependency:go-offline. After this call has succeeded you can build offline by adding the option -o or --offline to your Maven calls.

[Note]Note

Maven offers many command line options to improve efficiency by building only the required subset of modules. Especially the -pl, the -am, the -amd and the -rf options are interesting for your daily work. If, for example, you want to build all modules affected by your change in module X, you simply need to call mvn -pl ":X" -amd clean install from the root directory of the Blueprint workspace. If you don't want the dependent packages to be build, simply execute that call from within the modules directory.

If your build was successful, you can proceed with the next section. For a reference about all Maven build profiles, see Section 9.5, “Maven Profile Reference”