WFLY-2338 When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped
Upgrade Weld to 2.1.0.Final
WFLY-2223: fixes EE concurrent context service names conflicts, by retrieving the module name only when installing related services
WFLY-1631 Duplicated message ids in web, undertow, jsf and osgi subsystems
WFLY-2115: fixes initial context for URL schemes not implemented by Wildfly
[WFLY-2335] fix BroadcastGroupAdd model population on JDK8

Running tests with JDK8 revealed an issue with that code: there is no
guarantee when populating the broadcast-group model that the connector
resources have already been populated and that we can check them.
That seems to be the case with JDK7 but not with JDK8 (likely due to
Collections implementation details).

Fix this by checking the validation of connector-refs in another MODEL
OperationStepHandler ran *after* all the other MODEL's OSHs.
[WFLY-2291] Update messaging XML namespace to 2.0

The XML namespace for the messaging subsystem was erroneously bumped
from 1.3 to 1.4 for WildFly 8.

This is an error as the 1.x version must be reserved for AS7 7.x releases.
WildFly 8 must use a 2.0 namespace.
refactor messaging tests for resource transformers
[WFLY-490] / [WFLY-2258] Add sensitivity classification to 'describe' operation; actually enforce constraints on the READ_WHOLE_CONFIG ops
Update to HAL 2.0.5.Final
[WFLY-2332] Exclude jboss-logmanager from remoting-jmx, hornetq-journal and narayana-jts-jacorb
WFLY-490 / https://issues.jboss.org/browse/WFLY-2119 RBAC based tab-completion for the CLI (turned off by default)
[WFLY-490] [WFLY-2274] tests for reading standard/all-role-names
[WFLY-490] [WFLY-2190] [WFLY-2317] test for server-group add/remove
[WFLY-490] add missing license to an older test
[WFLY-490] [WFLY-2270] tests for model integrity checking
[WFLY-2336] The core size needs to be adjustined in line with the max size to avoid IllegalArgumentExceptions when modifying max-threads on an unbounded, queueless executor
[WFLY-2336] reorganized fix
[WFLY-2345] Port Offset 0 does not work

When a port offset is specified in the socket binding group and the
socket binding has a port of 0, then the port offset is not used to
calculate the port instead port 0 is bound.

This pull request contains three changes:

 - fix `SocketBinding` to also do offset calculation when the port is 0

 - extend `ControllerInitializer` to allow specifing the port offset

 - add a test in `OtherServicesSubsystemTestCase`

Issue: WFLY-2345
https://issues.jboss.org/browse/WFLY-2345
[WFLY-2296] propagate resulting version to runtime state