Rebranding

No change in functionality

Managed connection recovery

In release 3.0.0, with upgrade to com.rabbitmq:amqp-client:4.0.0 there was introduced bug #39. akka-rabbitmq doesn't act properly in case of disconnects, because newer amqp-client enables by default automatic recovery of broken connections.
Two recovery activities don't play nicely together, yet. They need a bit of time to get used to each other.
As a quickfix, before creating of connection factory settings are changed to disable autorecovery.

v3.0.0 (Long awaited)

Main changes

• cross-release for Scala 2.12/2.11
• upgraded amqp-client to version 4.0.0 (compatible with 3.x.x series)
• dropped Scala 2.10 support
• removed long ago deprecated parts

This release is last major release under com.thenewmotion organization.
Future releases will be under com.newmotion organization.

v2.2

Setting version to 2.2

v2.1

Setting version to 2.1