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

Creating the Maven Repository (Without Team Infrastructure)

Creating the Maven Repository (Without 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 unzip or checkout your source code to a directory 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 without a team infrastructure, which means your source code is not set up in Subversion and your Elastic Path artifacts are not deployed to a Nexus server.

The steps below describe how to set up your local .m2 repository with the Elastic Path repository artifacts so you can build your source code. For an overview of the source code structure, see Release Structure and Source Code Organization.

To set up your local .m2:

  1. Log on to the Elastic Path customer portal and download the Cortex API 1.9.0 archive by clicking Elastic Path Cortex 1.9.0 Source.
  2. Download the corresponding MD5 checksum file ( Elastic Path Cortex 1.9.0 Source MD5) and verify the integrity of the archive:
    • On Linux, check the MD5 checksum by following these steps:
      1. Run the following command in the directory you downloaded the source:
        md5sum Cortex-1.9.0.zip
      2. Open true_epZipFileName_source.md5 with a text editor and verify the hash in the file matches the hash printed out by the md5sum command.
    • On Windows, check the MD5 checksum by following these steps:
      1. Install Microsoft's File Checksum Integrity Verifier.
      2. Move the Elastic Path Cortex-1.9.0.zip into the Checksum Verifier's root directory.
      3. With the command prompt, navigate to the Checksum Verifier's root directory and run the following command:
        fciv.exe -add Cortex-1.9.0.zip
      4. Open true_epZipFileName_source.md5 with a text editor and verify that the hash in the file matches the hash printed out by the fciv.exe command.
  3. Unzip the contents of Cortex-1.9.0.zip to a directory named EP-rel in C:\. For example:

  4. With the Command Prompt, create a .m2 directory in your home folder. In Windows, the command is:
    mkdir C:\Users\<YourUserName>\.m2
    
  5. Copy developer-build-settings.xml from C:\EP-rel\Cortex\Repository to your .m2 directory.
  6. Rename developer-build-settings.xml to settings.xml.
  7. In your .m2 folder, create a directory named repository.
  8. Copy all the contents of C:\EP-rel\Cortex\Repository\binaries into your .m2\repository directory.

    Note: Windows Move Replace Warning

    Windows may display a Move and Replace popup warning window. It's OK to Move and Replace the files.