maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Siemon <>
Subject ForkedBooter in 2.2.1 does not honor MAVEN_OPTS
Date Sat, 20 Jul 2013 04:37:44 GMT
Specifically I have -Djava.awt.headless=true set in my maven options. Other
surefire booters seem to honor the headless mode and not steal focus but
the ForkedBooter still steals focus even when headless is set to true in

Running jps -v yields this view of the two maven jvms started:

Parent Maven with the correct MAVNE_OPTS
29028 Launcher -Xms2048m -Xmx4096m -XX:PermSize=1024m -XX:MaxPermSize=2048m

ForkedBooter without the maven opts. This process steals my screen each
time it runs.
29033 surefirebooter3016997434240550753.jar -XX:+HeapDumpOnOutOfMemoryError
-Xmx512M -XX:MaxPermSize=128M

maven version:

Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_51
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.8.4" arch: "x86_64" Family: "mac"

Upgrading from this version is not currently possible.

I am not sure why mvn is now using this forked booter in place of the
earlier one that honored MAVEN_OPTS. It might be that upstream changes in
parent artifacts are forcing me to run the ForkedBooter instead.

Thanks for any help you can offer.

*Ben Siemon*
Senior Software Engineer, Engineering
*Opower* <>

We’re hiring! See jobs here <>.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message