[WFLY-2415] Make legacy xml use statistics=true, which is the actual legacy behaviour
Prevent possible deadlocks relating to intermixing of parallel-capable and non-lockless class loaders
Revert "Use virtual file based resource manager to make sure deployment overlays work correctly with Undertow"

This reverts commit bd7fa6ed03188a74c89663826d7e6b77df64d8df.

This caused problems JSP, as getResource() on a jar would return the mounted directory, rather than the jar file.
WFLY-2598: fixes scheduledTimerFutures synchronization between timer creation and execution
[WFLY-2595] Rewrite the logging DUP's. Ensure the undeploy unregisters the log contexts so class loaders and log contexts aren't leaked.
WFLY-2398 fix InflowJarTestCase test fail on full profile
RESTEASY-991 Add integration test that JAX-RS components are CDI beans
with appropriate scope
https://issues.jboss.org/browse/WFLY-1063 Provide CLI preferences (support for variables)
[WFLY-671] re-enabled test, corrected assertion msg, reduced timezones
[WFLY-2609] Consistently use DeploymentManagementResourceRegistration where subsystems may mutate the deployment resource registration tree
[WFLY-2476] Improve security subsystem test coverage
add Principal to subject

Principal is only added to subject if we use RemotingConnectionCredential or when there is no Principal at all.
If we have valid principal we forget about it.

This causes org.jboss.security.auth.spi.RoleMappingLoginModule to be broken.
I'm not sure if this fix is correct (we can always get Principal from callbackHandler in LoginModule).

Another question what to do with roles? (JbossCallbackHandler don't contain this information) and what to do with roles added in LoginModule
[WFLY-2530] Add the operation header if removed by the transformer
[WFLY-2475] Fix marshalling of identity-trust's module
[WFLY-2474] Fix name and marshalling of acl's module + add transformers
[WFLY-2476] Security transformer improvements and better test coverage
WFLY-2618 : Intermittent 'AssertionError: expected:<200> but was:<500>' in org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload
The test was failing intermittently because per default the JVM is using HttpConnection with keep-alive and a timeout of 5s.
By setting the keep-alive to false in the setup and setting it to the value before the test on tear down we ensure a more stable test.
Merge commit 'refs/pull/5460/head' of github.com:wildfly/wildfly

Conflicts:
	clustering/infinispan/src/test/java/org/jboss/as/clustering/infinispan/subsystem/InfinispanSubsystemTestCase.java
Merge pull request #5548 from kabir/security-subsystem-fixes

Security subsystem transformer fixes
Merge pull request #5549 from dmlloyd/tempcl-deadlock

Prevent possible deadlocks relating to intermixing of parallel-capable a...