Hi, I'm running Hudson 1.297 with Maven 2.0.10 and JDK 1.5.0_17.

I have 3 slaves set up for building maven projects, each with 2 executors.

I currently have a recurring issue where some of the builds fail with an
OutOfMemoryError, even though the slaves themselves have an environment variable
of MAVEN_OPTS set, which quadruples the memory available to maven.

For some reason, when Hudson starts building a maven project, regardless of the
slave, this environment variable is ignored, and so my builds run out of memory.

I have noticed that in the configuration for each job the advanced options in
the maven section have a MAVEN_OPTS section.

I would like to suggest an enhancement that if the MAVEN_OPTS section of a build
is left blank, Hudson will look at the environment variables on the slave the
build is running on to try and find whether there is a MAVEN_OPTS already
defined. If one is found it should use it.