[Hawkular-dev] Manage cassandra-all in hawkular-parent

[John Sanda]

Definitely a good idea. And to be honest, I don’t see any reason not to move to Cassandra 2.2. H-Metrics might need to stay on 2.1.x for the OpenShift integration, but was can (easily) manage that separately.

> On Aug 7, 2015, at 4:21 AM, Peter Palaga <ppalaga at redhat.com> wrote:
> 
> Hi *,
> 
> ATM, cassandra-all is managed on three places independently, which is 
> hard to keep in sync:
> 
> org.apache.cassandra:cassandra-all occurences:
>   org.hawkular.metrics:cassandra-seed-provider:2.1.6
>   org.hawkular.commons:hawkular-commons-embedded-cassandra-service:2.1.6
>   org.hawkular.alerts:hawkular-alerts-engine:2.1.1
> 
> I'd put cassandra-all newest 2.1.* version (2.1.8) to 
> dependencyManagement in hawkular-parent unless somebody protests loudly.
> 
> Note, that we already manage 
> com.datastax.cassandra:cassandra-driver-core in parent. The driver's 
> release cycle is independendent from cassandra-all. The newest 2.1.* 
> version of the driver is 2.1.7.1 and I am going to upgrade to that one 
> in Parent.
> 
> Thanks,
> 
> Peter
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev