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 (Without Team Infrastructure)

Configuring Maven (Without Team Infrastructure)

Warning: Maven Settings Renaming Issue

The instructions below modify the Maven settings.xml file you added to your .m2 directly during 5. Source Code Preparation. Do not modify the settings.xml file in your Maven directory, which is at C:\apache-maven-3.0.4\conf.

These instructions configure your local Maven repository to retrieve build artifacts from your Nexus server and set up Maven to build for your specific environment, i.e Eclipse, Tomcat, and so on.

  1. With an XML editor, open your Maven .m2/settings.xml.
  2. Find and delete the following block of XML:
    <mirrors>
	<mirror>
	<!-- You will need to change the URL here to your corporate Maven repository which mirrors the internet. -->
	<id>internet-mirror</id>
	<url>http://your.internal.maven.repo.localdomain/nexus/content/groups/mirror</url>
	<mirrorOf>external:*</mirrorOf>
	</mirror>
 </mirrors>
  3. Comment out the ep-external-developer activeProfile:
    <!-- <activeProfile>ep-external-developer</activeProfile> -->
  4. Uncomment the following profiles:
    1. WTP Profile
      Profile Purpose 
      <activeProfile>wtp-developer</activeProfile>
      		Sets the Tomcat and the Search server ports to 8080, so they can run in Eclipse.
    2. Application Server Profile (uncomment one of these)

      Server

      Active Profile

      Tomcat

      		 
      
                           
                           <activeProfile>tomcat-developer</activeProfile>
  5. Save your modifications.