[WFCORE-9] Remove unused ExplicitTransformationDescriptionBuilder
[WFCORE-9] Unused code in ResourceTransformationContext(Impl)
[WFCORE-9] Chained resource transformer support
[WFCORE-9] Chained operation transformers
[WFCORE-9] Expose subsystem version from SubsystemRegistration
[WFCORE-9] Use proper ResourceTransformationContext impl for model-test and subsystem-test
[WFCORE-9] Enable placeholder registrations for subsystems
[WFCORE-9] Make the placeholder registry behave exactly the same as GlobalTransformersRegistry
[WFCORE-9] Use chained transformers for JMX subsystem
[WFCORE-9] Use chained transformers for remoting subsystem
[WFCORE-9] Use chained transformers for logging subsystem
[WFCORE-9] Chained core model transformers
[WFCORE-9] Simplify registration of chained transformers

Remove requirement for adding transformers for version deltas where no
transformation is needed.
[WFCORE-9] Cleanup

Use correct year in copyright headed of new classes
Fix some javadoc
[WFCORE-9] At the end of the resource only copy the affected model
[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.
[WFCORE-9] Remove unused log message
[WFLY-3362] cancel operations when the channel is closed
Merge pull request #39 from kabir/chained-transformers

Chained transformers
[WFLY-266] Notification Support

* add notifications to AS7 resources description
  notifications are described in :read-resource-description operation if
  the notifications boolean is true
* NotificationDefinition let any resources describe the notifications
  they can emit by registering them in the ManagementResourceRegistration
* add NotificationRegistry (exposed by the ModelController) to
  register/unregister notification handlers
* add NotificationSupport to emit notifications during a managemenet
  operations (through OperationContext.emit(Notification))

Notifications emitted by OperationContext.emit(Notification) are
effectively sent at the end of the operation execution if it is
successful. This ensure that the order of notifications emitted by a
single OperationContext will be received in the same order (unless they
are emitted during the ResultHandler execuion).

If the NotificationSupport is created with an ExecutorService, the
delivery of notifications is non-blocking and will not block the
remaining code path of the operation execution.

JIRA: https://issues.jboss.org/browse/WFLY-266