{"push_id":729532692,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"0b41bb7fe2aa3a7656b5d54d22c075bd9963f7e3","before":"4a54c5d83e9f2a2a9d86f81c21a3a08ca3d1c239","commits":[{"sha":"846dd075ae8b75ac8d2a589a85dcd8ae3635d020","author":{"email":"3503643d135e654b981cd46d1304f8cfa67a0b2e@gmail.com","name":"Jeff Mesnil"},"message":"JMX/Messaging-ActiveMQ Capabilities and Requirements","distinct":true,"url":"https://api.github.com/repos/bstansberry/wildfly/commits/846dd075ae8b75ac8d2a589a85dcd8ae3635d020"},{"sha":"5c33a65b30dc98e9835bf8d2800459aeefcf0a86","author":{"email":"3503643d135e654b981cd46d1304f8cfa67a0b2e@gmail.com","name":"Jeff Mesnil"},"message":"fix intermittent failures on JMSTopicManagementTestCase\n\nRemove assertion that a consumer can not receive a message after the\ntopic is closed. There is a time window where the messaging client may\nnot have been advertised that the topic has been removed and the\nconsumer must be closed.\nThis assertion is not relevant to the tests. Ensuring that removing and\nadding back the same topic removes all stored messages is enough","distinct":true,"url":"https://api.github.com/repos/bstansberry/wildfly/commits/5c33a65b30dc98e9835bf8d2800459aeefcf0a86"},{"sha":"c4e245b708f3661dfe656b50955a4fbc125fdc34","author":{"email":"0b0a8e9f80405c0c8fd49116fd90fab5ea8a47dc@redhat.com","name":"Brian Stansberry"},"message":"Merge pull request #7781 from jmesnil/fix_JMSTopicManagementTestCase\n\nfix intermittent failures on JMSTopicManagementTestCase","distinct":true,"url":"https://api.github.com/repos/bstansberry/wildfly/commits/c4e245b708f3661dfe656b50955a4fbc125fdc34"},{"sha":"0b41bb7fe2aa3a7656b5d54d22c075bd9963f7e3","author":{"email":"0b0a8e9f80405c0c8fd49116fd90fab5ea8a47dc@redhat.com","name":"Brian Stansberry"},"message":"Merge pull request #7771 from jmesnil/messaging-activemq-capability\n\nJMX/Messaging-ActiveMQ Capabilities and Requirements","distinct":true,"url":"https://api.github.com/repos/bstansberry/wildfly/commits/0b41bb7fe2aa3a7656b5d54d22c075bd9963f7e3"}]}