I found the reason, with 'mvn verify -Dwt.headless' maven does not pass
this parameter to the surefire/failsafe plugin. Maybe this changed since
maven 2.1, I can't remember that I had such problems with former maven
versions.
Therefore it is necessary to do:
...
//surefire
<plugin>
...
<configuration>
<argLine>-Dwt.headless</argLine>
...
</plugin>
Generally it would be nice, if wt.headless would also accept a
false/true value, so one could enable or disable it from mvn CLI:
<properties>
<!-- by default switched on -->
<wt.headless>true</wt.headless>
</properties>
...
<argLine>-Dwt.headless=${wt.headless}</argLine>
Currently just mentioning wt.headless makes the build headless.
manuel aldana schrieb:
when passing headless setting to maven;
mvn test -Dwt.headless
the test-running-console and browser with result page still is opened.
does somebody experience the same issue with 3.0?
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
--
manuel aldana
[email protected]
software-engineering blog: http://www.aldana-online.de
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
