[infinispan-dev] moving (some) cache stores in a different github repository

[Mircea Markus]

On 9 May 2013, at 22:13, Sanne Grinovero wrote:

> On 9 May 2013 21:38, Mircea Markus <mmarkus at redhat.com> wrote:
>> 
>> On 9 May 2013, at 16:03, Sanne Grinovero wrote:
>> 
>>> On 9 May 2013 15:10, Manik Surtani <msurtani at redhat.com> wrote:
>>>> This is something we discussed last year.  IIRC we agreed that all cache stores (except the 0-dep FCS) and hot rod clients will move out of the infinispan repo, and have their own repos.  They will also have their own release cycles, so will only be released as and when there is a change in their code.
>>> 
>>> I remember the discussion, but never agreed on it being a good idea.
>>> I'm not strictly against it, just that I am not understanding the
>>> point if it, while there are drawbacks.
>> pros: reduce distribution size, keep build time for the core manageable, allow a per/cachestore upgrade.
> 
> Is that the only advantage?
indeed the first one I mentioned could be achieved through packaging, but not the last two.
> Because the source control should have
> nothing to do with how the distribution is assembled.
> I still don't see why it's worth the effort,
it's a pretty straight forward task to move them out. Same to add CI job :-)
> and the pain.
If you're referring to the possibility of the cache store build to fail, I don't think this is negative thing as the core test suite should only get better.

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)