Question:

➜ ~ mvn

zsh: command not found: mvn

Answer:

step 1:

vim ~/.zshrc

step 2:(Add at the end of the file)

source ~/.bash_profile;

step 3:(Execution shell)

> source ~/.bash_profile

You can use mvn :

➜  / mvn

[INFO] Scanning for projects...
.......

If you are using zsh now, you may have to use ~/.zshrc rather than the ~/.bash_profile.

There is no reason for the command working without the 'sh -c', but who knows.

The mvn command is just a shell script which set the appropriate java environment to run java with the maven class. It uses /bin/sh because it is set in the first line of the script. If you want to use bash just change the first line of the script !/bin/sh by !/bin/bash.

Anyway, it seems your ubuntu is killing the compiler because it is taking more resources that it is allowed. Take a look to your /var/log/syslog file to see the reason why the kernel killed the build.

1- Try to reconfigure gwt-maven plugin in your pom.xml so as it only launches a worker

 <localWorkers>1</localWorkers>

2- try to increase memory of the gwt compiler process

 <extraJvmArgs>-Xmx1g</extraJvmArgs>

3- try to run maven with more memory

 $ export MAVEN_OPTS="-Xmx1g"

4- take a look to your shell ulimit and increase the appropriate parameters

 $ ulimit -a

The instructions you cited said to do this:

wget http://www.eng.lsu.edu/mirrors/apache/maven/maven-3/3.2.3/binaries/apache-maven-3.2.3-bin.zip
unzip apache-maven-3.2.3-bin.zip
mv apache-maven-3.2.3/ /opt/maven

This will result in /opt/maven/bin, /opt/maven/lib, etc.

What you did was slightly different:

wget http://www.eng.lsu.edu/mirrors/apache/maven/maven-3/3.3.1/binaries/apache-maven-3.3.1-bin.zip
unzip apache-maven-3.3.1-bin.zip
mkdir /opt/maven
mv apache-maven-3.3.1/ /opt/maven

This resulted in /opt/maven/apache-maven-3.3.1/bin, /opt/maven/apache-maven-3.3.1/lib, etc.

When you do mv x /y/z, where x is a directory, three different things can happen:

• if /y/z doesn't already exist, the entire tree rooted at x is moved to /y/z.
• if /y/z already exists and is a directory, the tree is moved to /y/z/x.
• if /y/z already exists and is not a directory, mv will output an error message and won't move anything.

My first guess would be that you're running out of memory, and the kernel is killing the compile process.