It seems a bit of a flaw in our test builds allowed us to miss a problem
with this release. Cassandra 1.2.x is intended to remain java_1.6
compatible, to the best of my knowledge. Unfortunately, CASSANDRA-7147
includes a bit of code that breaks the build when using Oracle JDK 1.6.
Should this be fixed for a 1.2.18 re-roll?
https://issues.apache.org/jira/browse/CASSANDRA-7147
--
Michael
On 06/30/2014 03:22 AM, Sylvain Lebresne wrote:
Including my own, I count 4 binding +1 and no -1's. The vote passes, I'll
get the artifacts published shortly.
On Thu, Jun 26, 2014 at 6:59 PM, Gary Dusbabek <gdusba...@gmail.com> wrote:
+1
On Wed, Jun 25, 2014 at 12:06 PM, Sylvain Lebresne <sylv...@datastax.com>
wrote:
I propose the following artifacts for release as 1.2.17.
sha1: 05fcfa2be4eba2cd6daeee62d943f48c45f42668
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.17-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1016/org/apache/cassandra/apache-cassandra/1.2.17/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1016/
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/8IIhDW (CHANGES.txt)
[2]: http://goo.gl/T2FKwT (NEWS.txt)
