gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BAZLEY, Sebastian" <Sebastian.BAZ...@london.sema.slb.com>
Subject java.awt.headless needed for current Gump builds
Date Mon, 08 Dec 2003 11:56:04 GMT
AIUI, java.awt.headless is a system property that can be set to indicate
that there is no X11 display available. 

Setting it may cause one or two AWT/Swing methods to fail with
java.awt.HeadlessException, but on the other hand it seems to avoid lots of
errors like:

java.lang.NoClassDefFoundError
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:140)
 	at
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment
.java:62)     

It seems to me that it would be sensible if the Gump builds either provided
an X11 display environment (e.g. Xvfb) or they should set
java.awt.headless=true.

At the moment, it looks as though LSD (utwente) is the only Gump that sets
the property; Covalent, Nagoya and Cocoondev do not set the property.

Would it be possible to fix this, either by setting the property, or
(better) by enabling a display environment?

==

java.awt.headless has to be set as a system property for it to have any
effect.
If the test target uses a different JVM, it appears that the property is not
propagated to the new JVM (is this a feature of Ant?), but the build file
can be tweaked to allow for this.

So setting the property would not necessarily work automatically, but would
allow projects to take appropriate action. 

At present, the only solution is to rely on some other setting that only
applies to Gump runs (I've done this for JMeter by adding a gump.run
property to the project file, but this is not ideal).

S.

Mime
View raw message