I am interested but haven't had a chance to look at it closely yet as it is
a big commit.  But I think it would be fine to be merged into 5.15 or even
5.14.2 since it is just an improvement for the junit support.

On Thu, Sep 29, 2016 at 9:52 PM, Quinn Stevenson <
[email protected]> wrote:

> I’ve had this PR open for a while now, but I haven’t heard anything back.
>
> If the community isn’t interested in this PR, please let me know so I can
> close it.
>
> > On Sep 16, 2016, at 3:09 PM, hqstevenson <[email protected]> wrote:
> >
> > GitHub user hqstevenson opened a pull request:
> >
> >    https://github.com/apache/activemq/pull/198
> >
> >    AMQ-6428 - Add methods to EmbeddedActiveMQBroker an ActiveMQ client
> JUnit Rules
> >
> >
> >
> > You can merge this pull request into a Git repository by running:
> >
> >    $ git pull https://github.com/hqstevenson/activemq AMQ-6428
> >
> > Alternatively you can review and apply these changes as the patch at:
> >
> >    https://github.com/apache/activemq/pull/198.patch
> >
> > To close this pull request, make a commit to your master/trunk branch
> > with (at least) the following in the commit message:
> >
> >    This closes #198
> >
> > ----
> > commit 343e3738b5cffdd6b95cfa257134108105f714c7
> > Author: Quinn Stevenson <[email protected]>
> > Date:   2016-09-16T20:59:13Z
> >
> >    Added methods to EmbeddedActiveMQBroker to send messages, as well as
> JUnit Rules for ActiveMQ clients
> >
> > commit f7b5b901004b90975cb82390684e89df57eaced4
> > Author: Quinn Stevenson <[email protected]>
> > Date:   2016-09-16T20:59:47Z
> >
> >    Merge branch 'master' of https://git-wip-us.apache.org/
> repos/asf/activemq into AMQ-6428
> >
> > commit 7be356017eecf37fa9c4884906e4eda06d8a6f19
> > Author: Quinn Stevenson <[email protected]>
> > Date:   2016-09-16T21:07:13Z
> >
> >    Added license header to files
> >
> > ----
> >
> >
> > ---
> > If your project is set up for it, you can reply to this email and have
> your
> > reply appear on GitHub as well. If your project does not have this
> feature
> > enabled and wishes so, or if the feature is enabled but not working,
> please
> > contact infrastructure at [email protected] or file a JIRA
> ticket
> > with INFRA.
> > ---
>
>

Reply via email to