OK CQL has been dropped from this release, I need two more binding +1's to release what remains (all & thrift)
On 28 April 2011 20:42, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote: > ok well I will see about deleting it from the staging repo, can I get a > conditional + 1 on that basis? > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 28 Apr 2011 20:31, "Eric Evans" <eev...@rackspace.com> wrote: > > On Thu, 2011-04-28 at 16:44 +0100, Stephen Connolly wrote: > >> > Unlike the RPC, CQL is meant to be stable. It is a significant > >> feature > >> > that you should be able to use the same version of a driver across > >> many > >> > versions of Cassandra. This is why the versions must be different, > >> so > >> > that you can evaluate each new driver version in the context of how > >> it > >> > changed, not (necessarily )how Cassandra changed during some > >> arbitrary > >> > release. > >> > > >> > >> This version number is all about versioning the information in the > >> __pom__. The pom defines transitive dependencies. You might not > >> rebuild the cql jar at all, but keep redeploying with different poms > >> (each getting their own version number... because we can only use a > >> version number once)... yes that is somewhat wasteful of space on the > >> central repository, but that's the way it works... [1] > >> > >> The 0.8.0-beta1 version number is only for the coordinates of the pom > >> of cassandra-cql that will pull down the dependencies for using cql > >> with cassandra 0.8.0-beta1. > >> > >> If that subtlety helps you understand the versioning I have chosen for > >> the poms, well that is better. > > > > It sounds to me like you need to omit the CQL jar entirely then, and not > > add it to Maven Central except as a different project. > > > > -- > > Eric Evans > > eev...@rackspace.com > > >
