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.

Updating Version Numbers

Updating Version Numbers

Overview

EP provides scripts to re-version projects and dependencies for:
  • Commerce Engine, Extensions, Devops and Commerce Manager projects
  • Cortex EP Integration project
Tip:

On Windows, use either Git Bash, MinGW, or Cygwin to run the script.

Assumptions

The examples on this page make the following assumptions:

  • All projects have a common parent folder.
  • Project folders have the same names as ones provided in source release packages.
  • The development branch is checked out for each project.
  • The projects are being reversioned to SNAPSHOT versions for development as recommeneded in Construction Practices - Version Numbers.

Versioning EP Commerce projects

This script versions all EP Commerce projects, except for the Cortex EP Integration project.

Example:

cd <projects-parent-folder>
         ./devops/scripts/set-ep-versions.sh 700.1.0-SNAPSHOT 0.0.0-SNAPSHOT commerce-engine extensions commerce-manager devops

Usage:

./set-ep-versions [-h] [-b] [-s <settings-file-location>] <commerce-engine-version> <extensions-version> <commerce-engine-directory> <extensions-directory> <commerce-manager-directory> <devops-directory>

Options:
    -h, --help
        Displays the help page

    -b, --build
        Builds the projects upon completing the version setting. By building the projects after setting their versions, 
        you verify the new version builds correctly.

    -s, --maven-settings <settings-file-location>
        Use a Maven settings.xml file that is not your default from your .m2 directory. This option can let you choose a relative path so each project
        can use a different settings from the same relative path of the project root.

The project directories can be relative or absolute paths. 

Versioning Cortex EP Integration

This script reversions the Cortex EP Integration project. If you don't reversion this project, then the Cortex EP Integration release binaries will be retrived from the Elastic Path Nexus repository.

You will need to reversion the project to a SNAPSHOT version if you wish to make changes.

Example:

cd <projects-parent-folder>
      ./devops/scripts/set-cortex-ep-integration-version.sh 700.1.0-SNAPSHOT 0.0.0-SNAPSHOT cortex-ep-integration extensions

Usage:

./set-cortex-ep-integration-version.sh [-h] [-b] [-s <settings-file-location>] <commerce-engine-version> <cortex-ep-integration-version> <cortex-ep-integration-directory> <extensions-directory>

Options:
        -h, --help
                Displays this help page

        -b, --build
                Builds the projects upon completing the version setting. By building the projects after setting their versions, you verify the new version builds correctly.

        -s, --maven-settings <settings-file-location>
                Use a Maven settings.xml file that is not your default from your .m2 directory.

The project directories can be relative or absolute paths.