Hi, I'm pretty sure lang3 isn't the only project that is affected, it's just the first one we've seen it. "we" ist the Gump project.
Sander has set up a Mac to run Gump[1] and commons-lang3 is Gump's guinea pig for Maven 3.x builds in the workspace we use for developer tests and new installations. The commons-lang3 builds fail[2] and too me it looks as if this was because AWT is not running in headless mode, this in [3] looks suspicious: java.lang.InternalError: Can't connect to window server - not enough permissions. As can be seen in [2] MAVEN_OPTS is set up to make mvn run in headless mode but it doesn't affect the tests - likely because the tests run in a forked VM and the same property must be set in the surefire configuration. I am suprised the problem doesn't show up in the other CI builds. There likely is a way we could set additional properties for the maven run (like surefire specific system properties or telling it not to fork), but (a) this is beyond my Maven foo and (b) would have to be repeated in other environments that have the same problem as well. Does anybody know of a better fix? Stefan [1] http://adam.apache.org/gump/ [2] http://adam.apache.org/gump/commons-lang-3.x/commons-lang3/gump_work/build_commons-lang-3.x_commons-lang3.html [3] http://adam.apache.org/gump/commons-lang-3.x/commons-lang3/gump_file/org.apache.commons.lang3.event.EventUtilsTest.txt.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
