[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- To complement [~NadirX]'s answer: since the Infinispan version used by WildFly *internally* is hard to replace, for example because it would require lots of clustering tests to be repeated, end user applications which wish to use Infinispan's latest version should use it as a separate module. The modules system will keep them strictly separated, and the modules provided by Infinispan are extensively tested for this scenario. The practical downside is indeed that you have to use the {{jboss-deployment-structure.xml}} or the manifest approach to have your application explicitly look for the {{ispn-8.0}} (or any version you'd like). The good news is that you'll always be able to use the latest version of Infinispan in your apps, without having to replace core components of the application server. So the infinispan-query (and some other extensions too) were removed from the internal dependencies as they are not being used by the clustering subsystem: you should use the better tested and maintained ones which are distributed by the Infinispan project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)