Maven build profiles are sets of configuration settings for building your software in different environments.
For example, if you have
tomcat-developer as an active profile, Maven builds your projects according to the
tomcat-developer settings, which in this case builds your web applications into a deployable Tomcat WAR.
Elastic Path defines a number of build profiles in
commerce-engine/pom.xml so you can build and deploy your Elastic Path Commerce platform on different application servers and databases. You can activate or deactivate the build profiles in your Maven
settings.xml file that is located in your
Application Server Profiles
The application server profiles are used to configure the type of WAR file generated by Maven. Choose the appropriate profile for your server.
Tomcat WAR with HTTP port
8080and HTTPS port
Additional profiles can be used to modify the Tomcat ports for for development:
Assigns separate ports for each webapp. See Running Webapps
If you switch application server profiles as you are developing, you must re-populate your database with the settings associated with these profiles
The database server profiles are used to configure the database the Elastic Path platform uses. Choose the appropriate profile for your database system.
mysql-dev-db- MySQL Database
oracle-dev-db- Oracle Database
mssql-dev-db- MSSQL Database
Code Compliance Profiles
The code compliance profiles control the level of code compliance checking.
Runs PMD and Checkstyle checks. Build fails if there are compliance errors.
Runs PMD and Checkstyle checks. Build passes if there are compliance errors.
Skips all code compliance checks
Packaging profiles control which packaging projects are in the
extensions/packager/ext-deployment-packagemodule, which creates a ZIP file that is used for creating Docker images.
extensions/packager/standalone-demomodule, which creates a standalone demo ZIP. The standalone demo ZIP contains all necessary components to start up Elastic Path web applications
Default profiles in
The global profiles that are active in the default extensions/maven/settings.xml file are:
Assigns separate ports for each web app. See Running Webapps.
Generates Tomcat WARs.
Configures MySQL database.
Configures Cortex to use OAuth 2.0 authentication.
Configures JMS (Java Messaging Service) to use ActiveMQ broker on port