I'l record a chat here which contains our debate and explanation on why the integration slot shall not contain the Infinispan version but rather the pattern for-hibernatesearch-5.3 - where 5.3 is the major.minor of the current search release.
<sannegrinovero> I'm trying to express that "twisted concept" of slot name which is then provided by a different project <sannegrinovero> ultimately the benefit would be that HS can build w/o having to define which Infinispan version will consume it <sannegrinovero> i.e. the slot encodes the HS version, not the Infinispan version. <gustavonalle> sannegrinovero, "for-hibernatesearch-5.3" slot name? shouldn't it be "ispn-8.0" ? <sannegrinovero> Makes sense right? Since the Infinispan build will know which version of HS it targets <sannegrinovero> you remember what we discussed on EAP 6.4 depending on JDG 6.5 using slot "jdg-6.4" right? <gustavonalle> yes <gustavonalle> sannegrinovero, it let me think in a name <sannegrinovero> ok, so I'm trying to use a better readable name to make it understandable <sannegrinovero> also, consider@ <sannegrinovero> - what if you decide to backport the upgrade to HS 5.3 to some other Infinispan 7.2 release <sannegrinovero> - what if you decide to stick to HS 5.3 in some other Infinispan release beyond 8.0 <sannegrinovero> .. <sannegrinovero> so I don't want to encode the Infinispan target version in the HS module <sannegrinovero> which implies Infinispan will release a module for a specific HS version it's testing successfully with <sannegrinovero> hence the pattern "for-hibernatesearch-5.3" <gustavonalle> sannegrinovero, at the end of the day, what matters is if they are compatible or not <sannegrinovero> lol <sannegrinovero> I guess the answer would be "most of the combinations are not compatible" ![](https://hibernate.atlassian.net/images/icons/emoticons/wink.gif) <gustavonalle> sannegrinovero, I don't know if 5.3 works with 8.0 tbh ![](https://hibernate.atlassian.net/images/icons/emoticons/smile.gif) <sannegrinovero> no but this HS release doesn't make assumptions on that <sannegrinovero> it's more that Infinispan will optionally provide a module which will work with 5.3 <sannegrinovero> or choose a different version.. <sannegrinovero> gustavonalle: keep in mind we need this to break out of the circularity: I must be able to release HS w/o any assumption on which Infinispan version will use it. <gustavonalle> sannegrinovero, yes, but this "optionally" means certain versions of search will not have the ispn directory at all? <sannegrinovero> that's possible. Up to us to try have at least one version, but it's not something that the rules of physics will enforce. <sannegrinovero> I call it flexibility ![](https://hibernate.atlassian.net/images/icons/emoticons/smile.gif) <gustavonalle> sannegrinovero, ![](https://hibernate.atlassian.net/images/icons/emoticons/smile.gif) <sannegrinovero> gustavonalle: it's also possible for one Infinispan version to publish aliases to satisfy multiple versions of Search. <sannegrinovero> gustavonalle: with this approach, the benefit is that it's the project running the integration tests which tells if it's going to be compatible (or not) and to which versions it's testing (if more than one, optionally) <gustavonalle> sannegrinovero, let's give a try... <sannegrinovero> we don't do multiple versions now but that's going to be handy when testing on multiple, long term supported platforms ![](https://hibernate.atlassian.net/images/icons/emoticons/wink.gif) <sannegrinovero> gustavonalle: ok so under this light, you like the name? <gustavonalle> sannegrinovero, alternative: ispn-hibernatesearch-5.3 <sannegrinovero> well remember it's ispn publishing this under namespace org.infinispan <sannegrinovero> so ispn is a bit redundant (and not the official name) <sannegrinovero> so I like the "for-" prefix to explain/remind of all the above ^ <gustavonalle> sannegrinovero, yes, the for create a nice natural language description of the module <gustavonalle> sannegrinovero, other idea "hibernatesearch-5.3-compat" <sannegrinovero> hum I think I would mistake it for some "compatibility module", like an adapter <gustavonalle> sannegrinovero, right <sannegrinovero> are you trying to find alternatives because you don't like the proposal? <gustavonalle> sannegrinovero, after understanding the motivation of it, your name makes sense, but my 1st reaction was weirdness ![](https://hibernate.atlassian.net/images/icons/emoticons/smile.gif) <sannegrinovero> ok well that's fine thanks I'll go with it then <gustavonalle> sannegrinovero, yeah, go for it, don't have any other better ideas
|