[WFLY-3406] :  Renaming invalidated jars.
 If the renaming couldn't be done during the patch application then it is tried during the next restart of the server.
[WFLY-3362] cancel operations when the channel is closed
[WFLY-3603] Add Global Resource Notifications

* add global notifications for resources:
  * resource-added when a resource is added to the management model
  * resource-removed when a resource is removed from the management
    model
  * attribute-value-written for resources that allow to write
    attributes when an attribute value is successfully changed.
    This notification contains a data set composed of:
    * name - the name of the attribute that has been changed
    * old-value - the value of the attribute before it was changed
    * new-value - the value of the attribute after it was changed

The old-value and new-value are *not* resolved (an attribute that is
undefined and has a default value will return "undefined" as its
old-value).

JIRA: https://issues.jboss.org/browse/WFLY-3603
[WFLY-3320] : Deployment scanner treats zipped content as managed.
When the deployment scanned is an archive then it is added to the content repository just like a file would be.
WFLY-3505 Check if service is up before using, to work around problem.
[WFCORE-20] TransformationTarget shouldn't expose the ExtensionRegistry
[WFCORE-20] Also get rid of unnecessary TransfomerRegistry.getExtensionRegistry()
prevent the http mgmt server from prematurely close the connections on shutdown
Merge pull request #53 from bstansberry/WFCORE-20

[WFCORE-20] Clean up use of ExtensionRegistry in the transformer classes
Merge pull request #40 from ehsavoie/WFLY-3406

[WFLY-3406] :  Renaming invalidated jars.
Merge pull request #45 from jmesnil/WFLY-3603_global_resource_notifications

[WFLY-3603] Add Global Resource Notifications
Merge pull request #50 from emuckenhuber/WFLY-3362

[WFCORE-19] properly cancel active mgmt operations on channel close
Merge pull request #51 from doctau/WFLY-3505

WFLY-3505 Check if service is up before using, to work around problem.
Used wrong WildFlySecurityManager method when attempting to invoke privileged actions.
Merge pull request #54 from jamezp/logging-fix

Used wrong WildFlySecurityManager method when attempting to invoke privileged actions
Undertow 1.1.Beta6
Merge pull request #55 from stuartwdouglas/undertow

Undertow 1.1.Beta6
Merge pull request #49 from ehsavoie/WFLY_3320

[WFLY-3320] : Deployment scanner treats zipped content as managed.
[WFLY-1878] : Current dev