6.4.0 Enhancements for Verbose API

The goal of this release is to simplify the usage of Verbose API. Following awkward user-cases have been simplified:

• #187
• #185
• #189

6.3.0

• Additive strategy for configuration replacement #177
• Depend on OSS Coherence CE instead of the commercially licensed #169
• Pull request builder has been moved to Github Actions from Travis CI #179 because of security reasons.

6.2.0 Support for ApacheIgnite Thin client

Support for ApacheIgnite Thin client #159

6.1.0 Support for refilling buckets over maximum

#151 Support for refilling buckets over maximum

6.0.0 Eliminate undefined behavior for configuration replacement

This release was inspired by user complaints:

• #133 Dynamically changing bucket configuration
• #135 I want to set Refill, Bandwidth capacity to 0

Special notes about version number and backward compatibility: This release breaks backward compatibility, that is why the major version was increased. 6.0.0 version is used instead of 5.0.0 because 5.0.0 is already reserved for release form 5.0 branch.

Backward compatibility has been broken in the following points:

• replaceConfiguration method now accepts an additional parameter.
• If you use native serialization for Hazelcast or Infinispan then binary serialized data is not compatible between 4.6.0 and 5.0.0, zero-downtime deployment can not be used in such use-case.

Verbose API

#117 Add current bucket configuration to ConsumptionProbe

4.9.0

New features in the release:

• #115 Compatibility with Hazelcast 4.x
• Support for Hazelcast 3.x marked as a legacy, but will be supported by a long time.

Note: for non-Hazelcast users there is no reasons to upgrade

4.8.0

New features in release:
#110 New API method consumeIgnoringRateLimits
#114 Support POF serialization for Oracle Coherence

4.7.0 Integration with native serialization for Hazelcast and Infinispan

Issue list:

• #108 Support "Custom Serialization" for Hazelcast
• #109 Support Protobuf serialization for Infinispan in order to be compatible with Infinispan 10.0

Compatibility with JPMS

Issue list:

• #106 providing Automatic-Module-Name via Manifest for compatibility with JPMS from java 9. Bucket4j itself is still written in java 8.