#Install maven for mac install
#Install maven for mac download
#Install maven for mac windows

#Install maven for mac download

For Linux: : Download and extract appropriate installation file for Linux 圆4.

#Install maven for mac windows

For Windows: Download and extract appropriate installation file for Windows 圆4.

In the Select a Target Operating System field, select an operating system. In the Select a Version of Java field, select 8. Your developer environment must meet the following minimum requirements:īefore you begin setting up your developer environment, you must set up either a team infrastructure environment or a Proof of Concept infrastructure environment with the following items:ĭevelopment on Elastic Path requires Zulu OpenJDK™ Java 8 ( 1.8.0_275 64-bit).

Import the projects into an IDE of your choice for development.

Build and run Elastic Path Web Applications from the command line.Zulu Open Java 8 JDK (Java Development Kit) 1.8 (64 bit)Īfter completing the setup instructions, you can:.If you’re are facing problems with finding JAVA_HOME you might also want to check this article on Stack Overflow: Where is JAVA_HOME on OSX Lion?.Following the instructions in this guide, you can set up a standard Elastic Path developer environment with the following: I didn’t have that file on my system so I created it with:Įcho JAVA_HOME=`/usr/libexec/java_home -v 1.7` | sudo tee -a /etc/mavenrcįinally Maven was picking up Java 7 both when run from the shell and from eclipse. It turned out that Maven loads settings from /etc/mavenrc if that file exists. Eclipse was started from a shortcut to Eclipse.app rather than a shell so the JAVA_HOME variable was not set. Now I tried to launch mvn from within eclipse but got “ Fatal error compiling: invalid target release: 1.7″. ~/bash_profile but I decided to keep them in ~/.profile and instead load it from ~/.bash_profile using:Īfter fixing the shell initialization files Maven was picking up Java 7 as expected. To use the settings in ~/.profile I could had moved them to. Looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. It turned out that brew had created a ~/.bash_profile file and the bash shell (from the bash man page): The JAVA_HOME environment variable was set in ~/.profile:Įxport MAVEN_OPTS='-Xmx512m -XX:MaxPermSize=128M'Įxport JAVA_HOME=`/usr/libexec/java_home -v 1.7`īut it was not exported. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Homeĭefault locale: en_US, platform encoding: MacRoman Java version: 1.6.0_41, vendor: Apple Inc. Maven home: /usr/local/Cellar/maven/3.0.4/libexec

Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Both Java 6 and Oracle Java 7 was installed on the system with the default JVM set to Java 7:

#Install maven for mac install

I had a Mac with OS X Mountain Lion (10.8.2) and Maven 3.0.4 (Maven installed using “brew install maven”). Recently I switched to Java 7 and then ran into a couple of issues.