Preparing Elastic Path Source Code

Prerequisites

Ensure that you have the following items:

• Access to Elastic Path Commerce Source and Maven repository
• A development branch created in your own Git repository

Configure Maven Settings for Team

In the development branch, update the extensions/maven/settings.xml file to reflect your project environment. When team members create their own branch from the development branch, they will have the necessary Maven configurations.

1. Check out the development branch that you created for your organization or team.

   For more information, see Getting Access to Elastic Path Commerce Source Code.

2. Open the ../extensions/maven/settings.xml file.

3. Replace PROJECT_REPOSITORY_GROUP_URL with the Nexus URL for <project> EP Repository Group.

   <mirrors>
       <mirror>
           <!-- You will need to change the URL here to your corporate Maven repository which mirrors the internet. -->
           <id>internet-mirror</id>
           <url>PROJECT_REPOSITORY_GROUP_URL</url>
           <mirrorOf>external:*</mirrorOf>
       </mirror>
   </mirrors>
   

   tip

   Depending on your installation, the URL is created in one of the following ways:

   • On-premises installation. You created the URL when you configured Nexus with the Maven repository for your team.
   • CloudOps installation. CloudOps deployed a Nexus server for you. See the CloudOps documentation to determine the hostname of the provided Nexus server, and use that to determine the full URL to the EP Repository Group based on the example below: http://<CloudOps_Nexus_Host_Name>/nexus/content/groups/ep-repository-group/

4. Make the required changes for your project environment.

5. Commit the changes and push them to your own Git hosting service.

Local Developer Environment Setup

Follow the instructions at Setting up your Developer Environment to configure, build, and run Elastic Path Commerce in a command line environment.