[ARTEMIS-595] When creating JMS bridge management API should pass bridge name to JMS broker #597
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dge name to JMS broker
bayern39
force-pushed
the
pass_birdge_name
branch
from
885954b
to
6fa979e
Compare
|
Commit messages should follow the 50/72 pattern as noted in the "Commit Messages" section on http://activemq.apache.org/artemis/docs/1.3.0/hacking-guide/maintainers.html. |
|
Go ahead and close this PR please. Tom sent #599 which has (most of) the appropriate changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/ARTEMIS-595