This page describes how to prepare Elastic Path source code for use by your project. The following diagram 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.3.0 Developer Guide:
   1. Java 8 (JDK 1.8 64-bit) setup
   2. Maven 3.5.2 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 use Git, convert line ending 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. This needs to be configured to connect to the project's Maven repository.

1. Replace the <mirror> <url> at 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 local ${user.home}/.m2 directory.

• Elastic Path source added to source control
• extensions/maven/settings.xml is configured correctly for local development