[
https://issues.jboss.org/browse/ISPN-4686?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on ISPN-4686:
------------------------------------
[~NadirX] It's fine to move classes around, but in a mature project it's wise to
retain but deprecate the old locations to ensure binary compatibility across releases.
The impetus for this JIRA is WildFly 9. I would like to use Infinispan 7 for WF9
clustering, but WF9 is stuck with Hibernate 4.3, which depends on Infinispan 6 - so binary
compatibility between 6.0 and 7.0 is essential for me to upgrade.
Moving forward, I've had requests from PM to allow users to upgrade the version of
Infinispan in WF/EAP post-release and have it magically work with the rest of WildFly/EAP
clustering. This won't work unless binary compatibility is preserved - and WF/EAP
references all of the the public classes mentioned in the description.
Make Infinispan 7.0 binary compatible with 6.x
----------------------------------------------
Key: ISPN-4686
URL:
https://issues.jboss.org/browse/ISPN-4686
Project: Infinispan
Issue Type: Bug
Affects Versions: 7.0.0.Beta1
Reporter: Galder ZamarreƱo
Assignee: Galder ZamarreƱo
Fix For: 7.0.0.CR1
The idea here is to try to produce a Infinispan 7.0 jar that's binary compatible with
6.0 in order to ease upgrading. So far, the following elements have been found to be
problematic:
* FileLookupFactory -> FileLookup changes - ISPN-3850
* JBossStandaloneJTAManagerLookup.init changes - ISPN-3850
* org.infinispan.AbstractDelegatingAdvancedCache refactoring to
org.infinispan.cache.impl.AbstractDelegatingAdvancedCache - ISPN-4074
XML configuration stays apart since one of the key aspects of 7.0 is to produce WF-like
configuration that's as close as possible, to improve usability between library and
server mode.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)