Aerospike Java client 4.1.11 adds the ability to switch between GNU and Bouncy 
Castle crypto libraries at compile time. Bouncy Castle has a MIT-based license.

Aerospike Java client 4.1.11 adds the ability to switch between GNU and Bouncy 
Castle crypto libraries at compile time.  Bouncy Castle has a [MIT-based 
license](https://www.bouncycastle.org/license.html).

There are now two Aerospike Java client libraries available on [Maven Central 
Repository](https://search.maven.org/search?q=aerospike-client).  The 
previously existing **aerospike-client** continues to link with GNU crypto.  
The new **aerospike-client-bc** links with Bouncy Castle crypto.

To use AerospikeClient with Bouncy Castle crypto, define this dependency in 
your pom.xml.

```xml
    <dependency>
      <groupId>com.aerospike</groupId>
      <artifactId>aerospike-client-bc</artifactId>
      <version>4.1.11</version>
    </dependency>
```
Aerospike requests that you restore AerospikeClient support with this new 
client library.


[ Full content available at: 
https://github.com/apache/incubator-pulsar/pull/2456 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to