[WFLY-2585] Accessing the current AccessControlContext needs to happen outside of the privileged action - otherwise the AccessControlContext is being replaced.
[WFLY-2587] Don't append =true to valueless system properties
[WFLY-2588] Handle additional quotes in system properties correctly
Introduce wildfly core distribution
Update welcome content
[WFLY-2583] Parse run-as role lists
https://issues.jboss.org/browse/WFLY-2574 use JAVA_HOME/bin/java instead of the default java on the path
[WFLY-2545] IronJacamar 1.1.2.Final
WFLY-2247 Add javax.transaction.api to JDBC module
WFLY-1858 Add RBAC sensitivity classification constraints to undertow subsystem
WFLY-2533 - Add ability to set default character encoding on a subsystem level
[WFLY-2364] ensure @Pool has a value
WFLY-2561: multi deployments using in-order may deadlock even if weld start service depends only on binder services
[WFLY-2586] Make the AddressValidator more lenient with IPv6 addresses specified the same as if they were a URL...
Allow specifying an empty security domain to disable security for an EJB
WFLY-2590: upon release of a stateful ejb instance, remove it from the cache if the timeout is zero
[WFLY-2218] Make LegacyKernelServicesInitializer.addMavenResourceURL() take a varargs of maven gavs
WFLY-2533 - fix typo
Undertow 1.0.0.Beta26
[WFLY-2469] Upgrade to HornetQ 2.4.0.Beta3

HornetQ depends on Netty 4 which has changed its package from
org.jboss.netty to io.netty.

* dependency changes:
  * upgrade HornetQ to 2.4.0.Beta3
  * add dependency to Netty 4.0.12 (GAV io.netty:netty-all:4.0.12)
  * adding picketbox as a dependency on hornetq, otherwise simple login
    modules won't work, also fixing the TCK after the update

* module changes:
  * add io.netty module for Netty 4.x (and keep org.jboss.netty module for
    Netty 3.x)
  * add hornetq-native jar to org.hornetq module (this jar contains now
    both Java classes and native libraries)
* management model changes:
  * remove servlet-connector resource that was using Netty 3.x HTTP
    tunneling Servlet and was added a workaround until HornetQ support
    one-port to be accessible over HTTP.