Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE #211] Remove the limitation that ExtRocketMQTemplate can not keep the same nameserver as RocketMQTemplate #212

Merged
merged 1 commit into from Jan 15, 2020

Conversation

RongtongJin
Copy link
Contributor

What is the purpose of the change

fix #211

Brief changelog

Remove the limitation that ExtRocketMQTemplate can not keep the same nameserver as RocketMQTemplate

Verifying this change

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist.
  • Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

…MQTemplate can not keep the same nameserver as RocketMQTemplate
@RongtongJin RongtongJin changed the title [ISSUE 211]:Remove the limitation that ExtRocketMQTemplate can not keep the same nameserver as RocketMQTemplate [ISSUE #211] Remove the limitation that ExtRocketMQTemplate can not keep the same nameserver as RocketMQTemplate Dec 24, 2019
@RongtongJin RongtongJin added the enhancement New feature or request label Dec 24, 2019
@RongtongJin RongtongJin added this to the 2.1.0 milestone Jan 10, 2020
@vongosling vongosling merged commit 0ae7904 into apache:master Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A template can only bind one group at present. How to implement multiple instances of rocketmq template?
2 participants