If the java code wasn't rebuilt doesn't that mean whatever we tried to add to cassandra.thrift, isn't actually available in this build?
On Tue, Nov 15, 2011 at 7:46 AM, Eric Evans <eev...@acunu.com> wrote: > On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne <sylv...@datastax.com> > wrote: >> So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take. >> Now that they are fixed, let's try again. I propose the following artifacts >> for release as 1.0.3. >> >> SVN: >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082 >> Artifacts: >> https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/ >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-186/ >> >> The artifacts as well as the debian package are also available here: >> http://people.apache.org/~slebresne/ >> >> The vote will be open for 72 hours (longer if needed). >> >> [1]: http://goo.gl/I1dZG (CHANGES.txt) >> [2]: http://goo.gl/PeD3Z (NEWS.txt) >> > > It looks like interface/cassandra.thrift has changed without the Java > code being regenerated. The test_describe system test is failing > because of this, (the versions don't match). > > Probably not justification for a re-roll, but not a great thing for > the release either... > > -- > Eric Evans > Acunu | http://www.acunu.com | @acunu > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
