Fix of Spring RabbitMQ integration test failures after spring update #2415
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
JiriOndrusek
force-pushed
the
spring-rabbitmq-failures-after-spring-update
branch
from
1faaeae to
6af91dd
Compare
oscerd
approved these changes
Mar 30, 2021
|
Follow-up issue: #2416 |
ppalaga
reviewed
Mar 30, 2021
There was a problem hiding this comment.
Great work, thanks @JiriOndrusek! Cosmetic suggestions inline.
extensions/spring-rabbitmq/runtime/src/main/doc/limitations.adoc
Outdated
Show resolved
Hide resolved
extensions/spring-rabbitmq/runtime/src/main/doc/limitations.adoc
Outdated
Show resolved
Hide resolved
JiriOndrusek
force-pushed
the
spring-rabbitmq-failures-after-spring-update
branch
from
6af91dd to
a461b1e
Compare
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.
fixes #2340
I created an issue in quarkus (quarkusio/quarkus#16117).
Once issue is fixed, new buildItem should be used and limitations.adoc could be removed.
I'll create a follow-up issue in camel-quarkus, to take care about it.
[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html