Re: Why is the CQL jar versioned independently?

2011-04-26 Thread Eric Evans
On Tue, 2011-04-26 at 22:42 +0100, Stephen Connolly wrote: > so will cql get its own tree from which releases well be cut, or will > it get released always at the same time? It would probably make sense at some point to separate the build for the Java client code so that releases could be made in

Re: Why is the CQL jar versioned independently?

2011-04-26 Thread Stephen Connolly
so will cql get its own tree from which releases well be cut, or will it get released always at the same time? - 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 26 Apr 2011 22

Re: Why is the CQL jar versioned independently?

2011-04-26 Thread Eric Evans
On Tue, 2011-04-26 at 13:31 +0100, Stephen Connolly wrote: > From what I can see, the intent is to always release lock-step in sync > with cassandra, in which case the version number should be the > cassandra version number... > > unless you are implying that this is "CQL version 1.0.0" and there

Why is the CQL jar versioned independently?

2011-04-26 Thread Stephen Connolly
Eric, In looking at the build, I see that the CQL jar gets its own version number... Does that make sense? >From what I can see, the intent is to always release lock-step in sync with cassandra, in which case the version number should be the cassandra version number... unless you are implying t