Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Configuring Maven (With Team Infrastructure)

Configuring Maven (With Team Infrastructure)

Warning: Windows Extractor Utility

There have been reports of problems when using Windows Extractor Utility to unzip Elastic Path and Eclipse archives, including password prompts and corrupted archive warnings. If you experience issues, try using a different extraction utility, such as 7Zip.

Warning: Windows File Path Limitation

Do not checkout your source code 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.

These steps assume you are setting up your developer environment within a team infrastructure, which means your Release Engineering group has already set up the source code in Subversion and has deployed the Elastic Path artifacts to their local Nexus.

  1. With the Command Prompt, create a .m2 directory in your home folder. In Windows, the command is:
    mkdir C:\Users\<YourUserName>\.m2
  2. Copy developer-build-settings.xml from <source release root>\Cortex\Repository to the .m2 directory.
  3. Rename developer-build-settings.xml to settings.xml.