https://issues.jboss.org/browse/WFCORE-50 CLI tests using non-standard output stream don't reset the terminal when done
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
[WFLY-3169] Emit local JMX notifications

* Emit JMX notifications based on WildFly's own notifications
* Notification is supported for JMX connections either in-vm (through
  ManagementFactory.getPlatformMBeanServer() or WildFly's
  MBeanServerService) and remotely if the JVM is started with the remote
  monitoring and management
* WildFly remoting-jmx does not support JMX notifications
* WildFLy notification are converted to their idiomatic JMX
  counterpart
  * WildFly's attribute-value-written is converted to JMX's
    AttibuteChangeNotification
  * WildFly's resource-added and resource-removed are converted to JMX's
    MBeanServerNotifications *and* emitted by the
    MBeanServerDelegateMBean (like regular MBeans)

JIRA: https://issues.jboss.org/browse/WFLY-3169
WFLY-3292: adding phase values for reworked EE resource definition processors
added message when there is roles associated and no roles
Update to 1.0.0.Alpha2 of wildfly-build-tools
Merge pull request #82 from jmesnil/WFLY-3169_local_JMX_notifications

[WFLY-3169] Emit local JMX notifications
Merge pull request #93 from aloubyansky/WFCORE-50-aesh-test-terminal

https://issues.jboss.org/browse/WFCORE-50 CLI tests using non-standard o...
Merge pull request #119 from emmartins/WFLY-3292

WFLY-3292: adding phase values for reworked EE resource definition proce...
[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.