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

Dinesh Joshi commented on CASSANDRA-9384:
-----------------------------------------

Good idea. Here are the updated patches for 2.1 and trunk. You might have to 
actually merge it up to 2.2, 3.0, 3.11.

 ||2.1||trunk||
|[branch|https://github.com/dineshjoshi/cassandra/tree/9384-cassandra-2.1]|[branch|https://github.com/dineshjoshi/cassandra/tree/9384-trunk-v2]|
|[utests & 
dtests|https://circleci.com/gh/dineshjoshi/workflows/cassandra/tree/9384-cassandra-2.1]|[utests
 & 
dtests|https://circleci.com/gh/dineshjoshi/workflows/cassandra/tree/9384-trunk-v2]|
||

> Update jBCrypt dependency to version 0.4
> ----------------------------------------
>
>                 Key: CASSANDRA-9384
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9384
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sam Tunnicliffe
>            Assignee: Dinesh Joshi
>            Priority: Major
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.11.x
>
>
> https://bugzilla.mindrot.org/show_bug.cgi?id=2097
> Although the bug tracker lists it as NEW/OPEN, the release notes for 0.4 
> indicate that this is now fixed, so we should update.
> Thanks to [~Bereng] for identifying the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to