[
https://issues.apache.org/jira/browse/CASSANDRA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989880#comment-14989880
]
Sylvain Lebresne commented on CASSANDRA-9543:
---------------------------------------------
bq. We are currently shipping an old release candidate of the 2.2 driver that
will never have a GA and is not even API compatible with the final 2.2 RC
And yet, to the best of my knowledge, there is not know bugs in our usage of it.
Again, our policy is we don't change dependencies in minor releases unless
there is a very good reason for it. I'm aware of no problems with the current
version shipped (that affects us), and I think that "allow people to run stress
with a version of the driver they use in their application" is neither all that
important not in practice (because stress is not _that_ good at emulating
realistic application workloads), nor completely practical (users will use a
variety of driver versions, including old ones), so I don't judge it a good
enough reason. But if enough person feels that this stress thing is important
enough to risk some destabilization, then so be it.
> Integrate release 2.2 java driver
> ---------------------------------
>
> Key: CASSANDRA-9543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9543
> Project: Cassandra
> Issue Type: Task
> Reporter: Robert Stupp
> Assignee: Jeremiah Jordan
> Fix For: 2.2.x
>
>
> Follow-up of CASSANDRA-9493.
> Hint: cleanup {{build.xml}} for commented out {{çassandra-driver-core}} maven
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
