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

We need an entry point guide for Messaging #39336

Closed
gsmet opened this issue Mar 11, 2024 · 2 comments · Fixed by #40586
Closed

We need an entry point guide for Messaging #39336

gsmet opened this issue Mar 11, 2024 · 2 comments · Fixed by #40586

Comments

@gsmet
Copy link
Member

gsmet commented Mar 11, 2024

Apparently, the guide in the SmallRye Reactive Messaging metadata was pointing to https://quarkus.io/guides/reactive-messaging which redirects to the Reactive Event Bus page and has nothing to do with our Messaging stack.

For now I dropped the guide from the descriptor as we need a working page but I think we need a https://quarkus.io/guides/messaging entry point with links to the various guides we have for messaging.

When created, we need to update the extension descriptor for the SmallRye Reactive Messaging extension.

@cescoffier does it make sense?

@cescoffier
Copy link
Member

Agreed, makes sense.

@quarkus-bot
Copy link

quarkus-bot bot commented Mar 12, 2024

/cc @MichalMaler (documentation), @ebullient (documentation), @inoxx03 (documentation), @michelle-purcell (documentation), @ozangunalp (reactive-messaging), @rolfedh (documentation), @sheilamjones (documentation), @sunayna15 (documentation)

@quarkus-bot quarkus-bot bot added this to To do in Quarkus Documentation Mar 12, 2024
@ozangunalp ozangunalp self-assigned this Mar 13, 2024
Quarkus Documentation automation moved this from To do to Done May 13, 2024
@quarkus-bot quarkus-bot bot added this to the 3.11 - main milestone May 13, 2024
@gsmet gsmet modified the milestones: 3.11 - main, 3.10.1 May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

4 participants