https://issues.jboss.org/browse/WFCORE-47 Enable operation arguments to accept special value characters
https://issues.jboss.org/browse/WFCORE-56 CLI --no-validation argument for cd
Merge from wildfly/8.x
implementation of WFLY-2510
added simple javabean to hold values instead of properties
use SimpleTable for output
added simple test
added help text
fix to remove bad chars
added ConnectionInfo interface and method getConnectionInfo to CommandContext to isolate responsibility
set ConnectionInfo to null if disconnected and re-create it when user re-connects
fix year of copyright. Only initialize ConnectionInfoBean after connection is sucessfull
username is retrieved from whoami operation
updated copyright year
added message when there is roles associated and no roles
[WFCORE-64] : Filesystem deployment scanner deployment failure removes unrelated deployments
Only deployments marked as PERSITENT=false (which means deployments made by the scanner) will be undeployed instead of all of them.
Since we don't have a simple way to link a deployment to a scanner this fix won't be enought for a multiple scanners case which is traced by WFCORE-65.
https://issues.jboss.org/browse/WFCORE-67 CLI shutting down a slave disconnects from the master
use jboss-parent 16
Upgrade to jboss-vfs 3.2.6.Final

Re licenced to ASL2
[WFCORE-69] Make available a ServiceController list so that the existing code does not trigger a NPE trying to access it.
[WFLY-266] Notification support

* Refactor the registry for the notification handlers by splitting the map
  into path segments to mitigate the o(n) cost.
* Rename the registry to NotificationHandlerRegistry and move it to the
  org.jboss.as.controller.registry package (leveraging the
  AtomicFieldUdpated of the package too)

JIRA: https://issues.jboss.org/browse/WFLY-266
Upgrade xnio to 3.3.0.Beta2 and jboss-remoting to 4.0.5.Beta1
[WFCORE-71] Don't use ProtocolLogger outside its own module