[infinispan-issues] [JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of WildFly

[Tristan Tarrant (Jira)]

     [ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-9964:
----------------------------------
    Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37  (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)


> Logging incompatibility when deploying modules on older versions of WildFly
> ---------------------------------------------------------------------------
>
>                 Key: ISPN-9964
>                 URL: https://issues.jboss.org/browse/ISPN-9964
>             Project: Infinispan
>          Issue Type: Bug
>          Components: WildFly modules
>    Affects Versions: 9.4.6.Final
>            Reporter: Ryan Emerson
>            Assignee: Ryan Emerson
>            Priority: Major
>             Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)