Building Self-Managed Commerce · Self-Managed Commerce

tip

New and redesigned build tools are available with the most recent releases of Self-Managed Commerce, and include build scripts that you can run locally or from within your continuous integration (CI) tool of choice. For more information, see Build Tooling Overview.

Prerequisites

Ensure that you have completed the following before you proceed to build Self-Managed Commerce:

Check-out the ep-commerce Git repository. See Source Code.
Configure your build environment. See Requirements for Setting up your Developer Environment.

Build All Projects

You can build all projects with one Maven command.

Open the command line and navigate to the Self-Managed Commerce source directory.
Run the following Maven command:
```
mvn clean install -DskipAllTests
```
With the -DskipAllTests command, the system does not run any unit test or integration tests, however the system still builds the test. For more details on the Maven arguments, see Elastic Path Maven Commands.

Build Individual Modules

You can also build each module in Elastic Path separately, if required. However, you cannot build the individual modules unless you build the Self-Managed Commerce source directory at least once. When you build the Self-Managed Commerce modules separately, you must follow the following order:

commerce-data
commerce-engine
health-monitoring
commerce-manager
cortex-resources
extensions

For example, when you build the commerce-manager module, you must first build the commerce-data and commerce-engine modules separately.

To build a modules individually, in the command line, navigate to the Self-Managed Commerce source directory.

Navigate to the project/module that you want to build.
Enter the following Maven command:
```
mvn clean install -DskipAllTests
```
With the -DskipAllTests command, the system does not run any unit test or integration tests, however the system still builds the test. For more details on the Maven arguments, see Elastic Path Maven Commands.