tag:github.com,2008:https://github.com/aspone/rabbitmq-java-client/releases Release notes from rabbitmq-java-client 2014-06-17T10:09:02Z tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_4 2014-06-17T10:09:02Z rabbitmq_v3_3_4 <p>Added tag rabbitmq_v3_3_3 for changeset 2a5910a64153</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_3 2014-06-12T15:20:16Z rabbitmq_v3_3_3 <p>Merge bug26232.</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_2 2014-05-22T01:44:16Z rabbitmq_v3_3_2 <p>merge bug26196 into stable</p> michaelklishin tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_1 2014-04-28T14:17:45Z rabbitmq_v3_3_1 <p>merge bug26145 into stable</p> rade tag:github.com,2008:Repository/21861418/rabbitmq_v3_3_0 2014-03-25T15:15:39Z rabbitmq_v3_3_0 <p>Merge bug26070.</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_4 2014-02-17T11:50:36Z rabbitmq_v3_2_4 <p>Merge bug 26014</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_3 2013-12-23T23:23:04Z rabbitmq_v3_2_3: fix timing and failure handling in testRestartingExpiry <p>...which was failing nearly all the time on my laptop</p> <ul> <li>publishing is async, so we don't know when the message has it the<br> server and hence the expiry timer starts. We could introduce a<br> confirm, but it's easier to just use the server restart as an<br> indicator.</li> <li>when the assertion fails we still need to delete the<br> queue. otherwise other tests using the same queue name, but<br> different params, will fail.</li> </ul> rade tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_2 2013-11-07T15:22:00Z rabbitmq_v3_2_2 <p>Added tag rabbitmq_v3_2_1 for changeset 892565568185</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_1 2013-10-25T17:19:47Z rabbitmq_v3_2_1 <p>Merged default into stable</p> grahamlittle tag:github.com,2008:Repository/21861418/rabbitmq_v3_2_0 2013-10-17T13:23:09Z rabbitmq_v3_2_0 <p>Merged stable into default</p> grahamlittle