See also...

Build BloomReach Experience Manager From Source

Introduction

Goal

Build any BloomReach Experience Manager open source project from source.

Background

BloomReach provides all BloomReach Experience Manager releases as open source to the community. Anyone can rebuild any project that is part of a BloomReach Experience Manager release from source and, if they wish, fork and modify it. The latter is very useful, for example, in case a developer wants to fix a bug or implement an improvement to be provided to the community as a patch.

Project Structure and Prerequisites

The BloomReach Experience Manager project has been split into a number of Maven projects. This allows separate release cycles and reduces the amount of code that will be rebuilt when only working on a sub-project.

You need to have the following installed to be able to build all BloomReach Experience Manager components:

Bloomreach only provides the Git trees for the release tags of BloomReach Experience Manager. Code changes which are under development for major, minor, or maintenance releases are not synchronized to the public community Git repositories. To find the tag of a project for a specific BloomReach Experience Manager release inspect the BloomReach Experience Manager release POM you are using (this is either the parent POM of your project in the case you using BloomReach Experience Manager, or the grandparent POM of your project in case you are using BloomReach Experience Manager) and check the version of the project you are using (you can also find this out by running mvn dependency:tree in your project).

By downloading BloomReach Experience Manager, you agree to comply with our open source license, as well as the licenses of other components we include in our distribution. For an extensive overview of open source licenses, see our page on licenses.