WFLY-3419 Only one jar in a module is scanned for beans.xml
Test for WFLY-3419
WFCORE-63 prepare for unified list serialization until we get new core release
WFLY-3881 User shouldn't be able to use empty JNDI name ('java:/' or 'java:jboss/')
WFLY-4021 add Hibernate ORM 4.3 module alias so applications or other modules can depend on the current org.hibernate:main version of Hibernate.  We should add an alias for the major/minor Hibernate orm release when changing org.hibernate:main in the future.
[JBWS-2680]:Fix authentication realm name hard-coded as "EJBServiceEndpointServlet Realm"
Fix WFLY-4034: Update to HAL-2.4.5.Final
Merge pull request #6889 from heiko-braun/WFLY-4034

Fix WFLY-4034: Update to HAL-2.4.5.Final
https://issues.jboss.org/browse/WFLY-4035 - Updating HornetQ 2.4.5.Final
WFLY-3900 test case
Merge pull request #6891 from clebertsuconic/master

https://issues.jboss.org/browse/WFLY-4035 - Updating HornetQ 2.4.5.Final
[WFLY-4038] close connections for a given JMS user

* add close-connections-for-user runtime operation to the hornetq-server
  resource to close any connections (JMS or core) opened by a given user

JIRA: https://issues.jboss.org/browse/WFLY-4038
[WFLY-4039] Close connections for consumers

* add close-consumer-connections-for-address to close connections
  for consumers that consumes messages from queues bound to the given
  address-match

JIRA: https://issues.jboss.org/browse/WFLY-4039
Merge pull request #6894 from jmesnil/WFLY-4038_WFLY-4039_close_connections_by_user_or_address

[WFLY-4038][WFLY-4039] Close connections by user or by address
[WFLY-3830] Use external-context for TIBCO EMS

Tibco EMS's JNDI provider is non-standard and accepts only CompoundName
in its lookup(Name) method while WildFly passes a CompositeName.

For such JNDI providers that accept only specific subtypes of Name, we
must instead use their lookup(String) method (that is more likely to
work as expectedi but comes with performance degradation as the whole
name would have to be parsed again).

If such a JNDI provider is configured in an external-context resource,
the presence of the org.jboss.as.naming.lookup.by.string property in the
external-context's environments with a value set to true will ensure
that the lookup(String) method is used. In any other case, the
lookup(Name) will be used.

JIRA: https://issues.jboss.org/browse/WFLY-3830
Merge pull request #6738 from jeffzhang/WFLY-3881

WFLY-3881 User shouldn't be able to use empty JDNI name ('java:/' or 'java:jboss/')
Merge pull request #6860 from stuartwdouglas/WFLY-3419

WFLY-3419 Only one jar in a module is scanned for beans.xml
Merge pull request #6863 from ctomc/mgmt-api

WFCORE-63 prepare for unified list serialization until we get new core release
Ugrade Hibernate ORM to 4.3.7
[WFLY-4016] fix memory leak on undeploy of ejb client deployment