Of course, any contribution is welcome!
I don't think we should commit to update all of them with each
Infinispan release, though - as you've seen, we don't always have the
resources to update and test them.
Cheers
Dan
On Mon, Jul 20, 2015 at 9:22 AM, Sebastian Łaskawiec
<slaskawi(a)redhat.com> wrote:
Hey!
+1000, that's great idea!
I think the first step is to update them and create CI jobs for them (at
least one for Pull Requests and one for SNAPSHOTs).
After that we could modify existing cache stores (at least Cassandra and
Mongo) and use Infinispan core dependency and not the parent. This would
allow us to use version ranges.
Does it make sense to put our Cache Stores into Infinispan release cycle?
This way the Cache Store version would be the same as Infinispan version.
Thanks
Sebastian
On 07/19/2015 11:45 AM, Andrea Cosentino wrote:
Hi,
Yesterday I've opened this ticket on github
https://github.com/infinispan/infinispan-cachestore-cassandra/issues/3
I'm interested in the different cachestore projects (mongodb, leveldb and so
on) and I'd like to see it revived by contributing to those projects.
Andrea
--
Andrea Cosentino
----------------------------------
Apache Camel Committer
Email: ancosen1985(a)yahoo.com
Twitter: @oscerd2
Github: oscerd
_______________________________________________
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