[ 
https://issues.apache.org/jira/browse/CASSANDRA-17354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724046#comment-17724046
 ] 

Abe Ratnofsky commented on CASSANDRA-17354:
-------------------------------------------

Looks like:
trunk is on 3.11.0: 
https://github.com/apache/cassandra/blob/trunk/.build/parent-pom-template.xml#L789
4.1 is on 3.11.0: 
https://github.com/apache/cassandra/blob/cassandra-4.1/build.xml#L649
4.0 is on 3.11.0: 
https://github.com/apache/cassandra/blob/cassandra-4.0/build.xml#L628

But...

3.11 is on 3.0.1: 
https://github.com/apache/cassandra/blob/cassandra-3.11/build.xml#L437
3.0 is on 3.0.1: 
https://github.com/apache/cassandra/blob/cassandra-3.0/build.xml#L409

Can we close this ticket out? I thought 3.0 and 3.11 were falling out of the 
support cycle once 5.0 is released.



> Bump java-driver dependency in Cassandra to latest 3.x series 
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-17354
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17354
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/unit
>            Reporter: Alex Petrov
>            Priority: High
>             Fix For: 5.x
>
>
> We depend on java-driver for testing, and developing/validating native 
> protocol changes. Unfortunately, the version of drvier that is  included with 
> Cassandra is quite ancient: 3.0.1. We need to bump this dependency to latest 
> in 3.x series, without upgrading to 4.0 at least for now. Unfortunately, this 
> is not a trivial change in build.xml (otherwise I would’ve done it rather 
> than opening this ticket), and bumping version breaks a few tests in all 
> versions, so those need to be fixed, too. 
> This should be a prerequiste for the next minor version release, too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to