[GitHub] activemq pull request: AMQ-5713 - making accessors public to remov...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq pull request: AMQ-5713 - making accessors public to remov...

asfgit
GitHub user mfrazier63 opened a pull request:

    https://github.com/apache/activemq/pull/106

    AMQ-5713 - making accessors public to remove startup error.

    Includes unit test DestinationBridgeAccessorsTest which replicated the problem and now passes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mfrazier63/activemq AMQ-5713

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/106.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 #106
   
----
commit dcc7b11347fbaa91e6e387fdb8b0dfd67f719287
Author: mfrazier <[hidden email]>
Date:   2015-05-29T23:13:41Z

    AMQ-5713 - making accessors public to remove startup error.
   
    Includes unit test DestinationBridgeAccessorsTest which replicated the problem and now passes.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq pull request: AMQ-5713 - making accessors public to remov...

asfgit
Github user asfgit closed the pull request at:

    https://github.com/apache/activemq/pull/106


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---