This page describes how to prepare Elastic Path source code for use by your project. The diagram below shows the steps.

You will need a working Java build environment on your local computer to prepare the source code.

1. Setup your build environment as described in the following sections of the Core Commerce 6.16.0 Developer Guide:
   1. Java 8 (JDK 1.8 64-bit) setup
   2. Maven 3.3.9 setup
   3. Configure your System Environment Variables

EP source is delivered in multiple ZIP files. You should obtain one or more of the following release packages depending on your license and the environment you wish to create:

• Unzip the contents of the release packages into your project source folder.
  Warning: Windows File Path Limitation

  Do not save your source projects to a directory that is greater than 20 characters in length. Windows file paths are limited to 260 characters. The longest file path in the source code is greater than 230 characters so be careful where you deploy your source files.

1. Add the following projects to source control as separate repositories: cmclient, commerce-engine, devops, extensions, and the ep-aem-commerce & geometrixx-demo projects if applicable.
   Tip:

   If you use GitHub or a similar Git hosting service, follow the instructions in Add Source to GitHub.

   Tip:

   The commerce-data project is included in the release package for reference and doesn't need to be added to source control.

   The cortex-ep-integration project is provided to make it easier to extend Cortex integration bundles. It can be added to source control and incorporated into your build process at a later time if needed.

2. Create a development branch for each project. The branch name depends on your SCM and branch naming conventions.

The extensions project you just added to source control has a maven/settings.xml the project teams will use.

1. Replace the <mirror> <url> at the the top of the file with the <Project> EP Repository Group URL documented during Setup Maven Repository.
2. Make any changes required for your project environment.
3. Commit the changes to source control.
4. Copy the settings.xml to your ${user.home}/.m2 directory.

If you do not have a license for EP Commerce for AMC, you need to remove related dependencies from the extensions project source. Otherwise the build will fail when it attempts to get artifacts from Elastic Path Maven repository groups to which you don't have access.

The devops project: contains modules to remove EP Commerce for AMC references from the extensions project source:

EP release packages contain projects with RELEASE versions. Prior to starting development, the projects must be reversioned to SNAPSHOT versions.

• All EP projects added to source control
• Projects have development branches with SNAPSHOT versions
• extensions/maven/settings.xml is configured correctly for local development