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.

Elastic Path Maven Commands

Elastic Path Maven Commands

All Elastic Path Commerce projects are Maven projects with configurable pom.xml files. The POM files contain configuration details and dependency information required for building, installing, cleaning, packaging, and running projects in development and CI environments.

This page lists some of the commonly used Maven commands with Elastic Path Commerce.

Note:

When running Maven commands you may experience a java.lang.OutOfMemoryError: unable to create new native thread error. To solve this issue increase the memory setting in the MVN_OPTS environment variable.

Building Projects

To build a project, navigate to the project folder (e.g. extensions/cortex) and execute one of these commands:
Goal Command
Build project and execute all integration tests mvn clean install
Build project without running integration tests mvn clean install -DskipAllTests

Running Webapps

To run a web application as a standalone process, navigate to the webapp module (e.g. extensions/cortex/ext-cortex-webapp and execute one of these commands:

Goal Command
Run webapp without debugging 
mvn clean tomcat7:run-war
Run webapp with external debugging on port 8000 mvnDebug clean tomcat7:run-war
Note:

To run web applications as separate processes, the ep-developers profile must be active and wtp-developers profile inactive. For more information see Elastic Path Maven Profiles.

The ep-developers profile assigns the following web application ports:

  • 8081 - Commerce Manager server
  • 8082 - Search server
  • 8083 - Integration server
  • 9080 - Cortex and Cortex Studio

Running ActiveMQ

The ActiveMQ broker can either be installed as a service on your computer or run from the command line from extensions/activemq-broker module.

Goal Command
Run ActiveMQ broker from command line 
mvn clean tomcat7:run-war

Testing and Code Compliance

The ActiveMQ broker can either be installed as a service on your computer or run from the command line from extensions/activemq-broker module.

Goal Command
Run an individual JUnit test mvn install -Dtest=<TestClassName>
Run an individual JUnit Integration test mvn install -Dit=<TestClassName>
Run PMD to check for common programming flaws mvn pmd:check
Run Checkstyle to validate code formatting and style mvn checkstyle:check
Check for licensing compliance mvn licensing:check

Populating the Database

Data population commands are run from the extensions/database module.

Goal Command
Delete database schema, then create and populate the database mvn clean install -Preset-db
Update the database mvn clean install -Pupdate-db

Common Build Sequences

As a development best practice, you may want to script common build sequences. Here are some examples:

Goal Commands
Change ep-core logic, update the ext-commerce-engine-wrapper, then debug in Cortex 
mvn clean install -f commerce-engine/core/ep-core/pom.xml
mvn clean install -f extensions/cortex/ext-commerce-engine-wrapper/pom.xml
mvnDebug clean tomcat7:run-war -f extensions/cortex/ext-cortex-webapp/pom.xml
Change ext-core logic, then debug in Cortex 
mvn clean install -f extensions/core/ext-core/pom.xml
mvnDebug clean tomcat7:run-war -f extensions/cortex/ext-cortex-webapp/pom.xml