[jboss-jira] [JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107842#comment-13107842 ] 

Sanne Grinovero edited comment on WFLY-4695 at 9/11/15 8:11 AM:
----------------------------------------------------------------

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}} slot (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.


was (Author: sannegrinovero):
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.

> Remove infinispan-query module and its dependencies
> ---------------------------------------------------
>
>                 Key: WFLY-4695
>                 URL: https://issues.jboss.org/browse/WFLY-4695
>             Project: WildFly
>          Issue Type: Task
>          Components: Clustering
>            Reporter: Sanne Grinovero
>            Assignee: Paul Ferraro
>             Fix For: 10.0.0.Beta1
>
>
> We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly.
> Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)