-Djava.awt.headless works also and does not open the console, never the
less with this env, webtest still tries to open a browser window.
In the end the wt.headless is more appropriate because it switches
browser linkage off also.
Victor Ott schrieb:
> Yes, you're right about wt.headless:
>
http://mguillem.wordpress.com/2009/04/30/webtest-with-groovy-maven-and-eclipse/>
http://groovy.dzone.com/news/webtest-groovy-maven-and>
> *g* how did I miss it?
>
> For non-WebTest Maven:
>
http://marc.info/?t=113021227600003&r=1&w=2
> <
http://marc.info/?t=113021227600003&r=1&w=2>
>
>
> Grüße,
> Victor
>
> On Tue, Jun 23, 2009 at 2:36 PM, manuel aldana <
aldana@...
> <mailto:
aldana@...>> wrote:
>
> It is documented as wt.headless
> (
http://webtest-community.canoo.com/jira/browse/WT-344).
>
> -Djava.awt.headless=true does not work either.
>
> Can anybody reproduce the headless config problem?
>
> Victor Ott wrote:
>
> Was it a typo only in your email? It's "java.awt.headless",
> not "wt.headless":
>
> -Djava.awt.headless=true
>
>
> On Sun, Jun 21, 2009 at 11:39 PM, manuel aldana <
aldana@...
> <mailto:
aldana@...> <mailto:
aldana@...
> <mailto:
aldana@...>>> wrote:
>
> Amelia A Lewis schrieb:
>
> On Sun, 21 Jun 2009 19:29:55 +0200, manuel aldana wrote:
>
> when passing headless setting to maven;
> mvn test -Dwt.headless
>
>
> Try mvn test -Dwt.headless=true (or any random value). ant
> -Dproperty doesn't have the same effect as ant
> -Dproperty=value, even if you're only using the
> property for
> if/unless and isset.
>
> Forgot to mention, tried out this option already. But no
> success.
>
> -- manuel aldana
>
>
--
manuel aldana
aldana@...
software-engineering blog:
http://www.aldana-online.de_______________________________________________
WebTest mailing list
WebTest@...
http://lists.canoo.com/mailman/listinfo/webtest