[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=13078549#comment-13078549 ] 

Sanne Grinovero commented on WFLY-4695:
---------------------------------------

[~alesj] we're not stopping the Infinispan Query project, you just have to use the modules provided by the Infinispan project. That also better matches the model of the products: Infinispan Query is an add-on feature which isn't included in EAP but requires an optional layer.
To configure it, you configure Infinispan as usual but that is done either programmatically or using a dedicated Infinispan configuration file, not by editing the configuration of the app server. That's an important difference as the Cache configuration sections of the app server related to the Infinispan version (module slot) as shipped with WildFly, while you want to use the Infinispan version which you're adding as a layer.

That will benefit CapeDwarf in terms of speed: it means you can always pick and choose which version of Infinispan suits you best, so you can use any Infinispan version tagged last night without having to wait for a WildFly release to include it. Means you can benefit from Infinispan fixes overnight, that should speed us up all and remove quite some alignment overhead.

> 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: Sanne Grinovero
>
> 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.3.15#6346)