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 7.1.0 Developer Guide:
   1. Java 8 (JDK 1.8 64-bit) setup
   2. Maven 3.3.9 setup
   3. Configuring System Environment Variables

Elastic Path Commerce source code is delivered in the following release package:

• Unzip the contents of the release package into your project source directory.

1. Add all files in the ep-commerce directory to source control.
   Tip:

   If you are using Git, line endings need to be converted to LF on input.

   The command to configure this is:

   git config --global core.autocrlf input

   • Create a development branch in the project repository. The branch name depends on your SCM and branch naming conventions.

The extensions module you just added to source control has a maven/settings.xml file 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.

Elastic Path release packages contain modules with RELEASE versions. Prior to starting development, the modules must be reversioned to SNAPSHOT versions using scripts provided in the devops module.

To re-version modules for development:

• All Elastic Path modules added to source control
• Modules have development branches with SNAPSHOT versions
• extensions/maven/settings.xml is configured correctly for local development