Hi Marc,
yes, I traced the problem down last week and the only explanation was:
If I set the proxy by ant-task: <setproxy> in the upper build.xml, they are not available in the
lower build.xml and therefore the webtests are not aware of the proxy.
As far as I know the ant-task(proxy) adds the property to the system.properties useable for this
jvm. A newly started jvm starts with the clean collection of system.properties, nothing about the proxy.
Michael
Marc Guillemot wrote:
Is there a reason webtest only considers System.properties?
because this is what is set by the <setproxy> Ant task.
Do you say that if you use <setproxy> in your upper build.xml, the proxy
settings aren't available for the called build files? This would be
really strange are system properties should be global, no matter what
you set for InheritAll.
Marc.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
--
Mit freundlichen Grüßen
------------------------------------------------------------------------
Michael Habbert
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
