If you are running Aspire with the Quick-Start Distribution from the aspire binaries, you can skip this part, otherwise If you are using the Maven Archetype for downloading Aspire you must follow this section.
Installing the Maven command line is a very useful way to work with Maven and projects (especially for distributions), or when you're having trouble with m2eclipse (which happens now and then).
Without typing any spaces, enter the the bin directory from Apache Maven to your environment path (for example, ;C:\dev\apache-maven-3.3.9\bin) and click OK .
At the prompt, enter: mvn -version and then press Enter.
Success is indicated when version information is returned, such as the following:
> mvn -version Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T10:41:47-06:00) Maven home: C:\dev\apache-maven-3.3.9 Java version: 1.7.0_79 Java home: C:\dev\jdk1.7.0_79\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
.m2/settings.xml
file to point to the Search Technologies repository.The easiest method for creating new components and new distributions with Aspire is to use the Search Technologies Maven repository for Aspire.
The Maven repository is available from the following URL:
You will need to register with with Search Technologies before you can connect up to the Search Technologies Maven repository.
In order to use the Maven repository (either within Eclipse or on the command), you will need to add the following to your Maven settings file. There are two possible locations for the maven settings file:
Probably the user-specific version is safer and is most likely to be picked up by both the Maven command line and Maven for Eclipse.
Once you have registered, use your registered username and password to replace "REGISTERED-USERNAME" and "REGISTERED-PASSWORD" below.
For this process we assume the user has created the M2_HOME, to see how to create the M2_HOME please go to Install Maven
<?xml version="1.0" encoding="UTF-8"?> <!-- ******************************************************************************************** ** ** Copyright Search Technologies 2016 ** **~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ** ** Aspire Maven settings.xml ** ** This file is configured by default to run in "public" mode, connecting to ** https://repository.searchtechnologies.com/artifactory/public ** ** There are two profiles: ** ** server: sets the stRepositoryServer variable (used in all urls) to point to the main ** Artifactory server (default) ** ** public: sets the repository url to ${stRepositoryServer}/artifactory/public ** This is the main (default) profile for general use. The public repository ** covers the release repository and the "stable" snapshots --> <settings> <servers> <server> <id>stPublic</id> <username>REGISTERED-USERNAME</username> <password>REGISTERED-PASSWORD</password> </server> </servers> <profiles> <profile> <id>server</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <!-- Search Technologies' Artifactory server --> <stRepositoryServer>https://repository.searchtechnologies.com</stRepositoryServer> </properties> </profile> <profile> <id>public</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <!-- Artifactory URL --> <stPublicUrl>${stRepositoryServer}/artifactory/public</stPublicUrl> </properties> <repositories> <repository> <id>stPublic</id> <url>${stRepositoryServer}/artifactory/public</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </releases> </repository> <repository> <id>cloudera</id> <url>https://repository.cloudera.com/artifactory/cloudera-repos</url> </repository> </repositories> </profile> </profiles> </settings>