On 11/15/2011 12:47 AM, Steve Gordon wrote:
>> $> mvn --version
> Apache Maven 2.2.1 (rNON-CANONICAL_2011-10-11_11-56_mockbuild;
> 2011-10-11 07:56:30-0400)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-1.6.0-openjdk-18.104.22.168.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "3.1.0-7.fc16.x86_64" arch:
>> also can you please try running this without the 'clean' phase, i
>> to see if it is related to some kind of timeout
>> mvn install -Pgwt-admin,gwt-user -DskipTests=true -X
> I'm running this again now, only have access to the laptop today so
> will probably be a while until I can report back :).
This produced the same result (error). Based on Doron's suggestion earlier in the
thread I decided to throw more memory at the problem. I then received a
java.lang.OutOfMemoryError: PermGen space error, setting
MAVEN_OPTS="-XX:MaxPermSize=128m" seems to have fixed this and I have now built
sucessfully. Thankyou for your suggestions!
I have added the perm gen space error tip to
, more generally we probably need to
consider some hints/recommendations around what kind of computing power (particularly
memory) is required to successfully compile the project.
I Googled around it a little but could not find anything obvious.
what i did found is this -
"If you use Unix/Linux:
Exit-code above 128 means that the process died because of a received
signal (exitCode = 128 + signalNumber).
==> In your case it was signal 9 (= SIGKILL)."
Not sure it can give you a lead but the next step i would try is
compiling without the UI -
$OVIRT_HOME> mvn install -DskipTests=true