While running through a build of Wildfly on a system that requires using a proxy, I amend the JVM runtime arguments using the surefire.extra.args property, set to -Dhttp.proxyHost=<proxy> -Dhttp.proxyPort=<port> et al.  This results in the proxy being passed into the maven resolver used by many of the wildfly tests.

For whatever reason, this does not appear to work for the wildfly-ee-galleon-pack-layer-tests.  I traced calls through wildfly-glow and it appears no default proxy settings are being created when the maven resolver is invoked via wildfly-glow functionality in the test.  I have not been able to pinpoint where proxy information is getting lost nor have I been able find anything that indicates how these tests in particular would require proxy configuration information to get set.