Quantcast

[GitHub] activemq-artemis pull request #1219: JDBC update and test fix

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

[GitHub] activemq-artemis pull request #1219: JDBC update and test fix

asfgit
GitHub user andytaylor opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1219

    JDBC update and test fix

   

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

    $ git pull https://github.com/andytaylor/activemq-artemis ARTEMIS-1125

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

    https://github.com/apache/activemq-artemis/pull/1219.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 #1219
   
----
commit 9c013e74cba7ee4b3bc766029ff43c3b306ba4d5
Author: Martyn Taylor <[hidden email]>
Date:   2017-04-20T17:31:24Z

    ARTEMIS-1125 Persist JMS Bindings in Database on JDBC

commit 56a18759a7117c19330b2d913753e55cd60f7231
Author: Andy Taylor <[hidden email]>
Date:   2017-04-21T09:39:25Z

    no jira - fix test

----


---
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
|  
Report Content as Inappropriate

[GitHub] activemq-artemis pull request #1219: JDBC update and test fix

asfgit
Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1219


---
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.
---
Loading...