Re: [infinispan-dev] moving (some) cache stores in a different github repository
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.
Now when it comes to breaking stuff, this means that our CI will get more complex. Any
changes to core will cause a build and re-test of all "consuming" projects
(cache stores and hot rod clients). Failures on any of these "consuming"
projects should cause a failure in core's CI suite.
On 9 May 2013, at 14:13, Sanne Grinovero <sanne(a)infinispan.org> wrote:
With independent release numbers (and days) ?
I realize it makes developer's life easier as you can break them all
without needing to care, still it won't make users life easier.
What do you propose we should do when an Infinispan (core project)
change breaks some tests in the CacheStore?
On 9 May 2013 14:07, Adrian Nistor <anistor(a)redhat.com> wrote:
> I think it makes sense to move all of them to a separate project, except
> FileCacheStore. I doubt there is real need for a zip distribution for
> this new project.
>
> We can continue to provide a zip for the main ispn project, but I still
> think few people actually use it compared to the maven artifacts. I
> believe the main reason for a zip distro is to be able to accurately
> count the number of downloads :).
>
> On 05/09/2013 03:22 PM, Mircea Markus wrote:
>> Hi,
>>
>> Because of the hight number of dependencies and large distribution size (build
time as well) there were discussions about moving some of the cache stores into an
independent git repository under the infinispan project. Now that we have two more cache
stores to be integrated (JPA and MongoDB), it's a good opportunity to start a
discussion around this.
>>
>> The cache stores I'm thinking about are: JPA, MongoDB (integrated them
directly in the new repository), Cassandra, Cloud, HBase, jdbm and bdbje. Or thinking more
about it, why not all of them but the file cache store - which is dependency free and
it's nice to ship it .
>>
>> There are several options when it comes to releasing these stores. I think the
simplest is by to a maven repo (i.e. no .zip file). If there'll be demand for specific
distribution files we can always add it at a further point in time.
>>
>> wdyt?
>>
>> Cheers,
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid