Do we need to keep project creation with archetype? This is not standard approach. I think we can remove whole Creating the Maven Project chapter.

Do we need to keep project creation with archetype? This is not standard approach. I think we can remove whole Creating the Maven Project chapter.

For now I would prefer to not touch that. In the future with the help of new tooling we should revise tho.

Then we should update a dependencies which we instruct a user to add it. I mean the resteasy-jaxrs dependency. The used BOMs doesn't contains its version. The QS pom.xml using the resteasy-core-spi artifact.

https://github.com/emmartins/quickstart/blob/WFLY-21104/microprofile-reactive-messaging-kafka/README-source.adoc?plain=1#L167

Then we should update a dependencies which we instruct a user to add it. I mean the resteasy-jaxrs dependency. The used BOMs doesn't contains its version. The QS pom.xml using the resteasy-core-spi artifact.

https://github.com/emmartins/quickstart/blob/WFLY-21104/microprofile-reactive-messaging-kafka/README-source.adoc?plain=1#L167

Fixed, thanks.

For now I would prefer to not touch that. In the future with the help of new tooling we should revise tho.

Also a content of All classes is different and not build-able when i am followup the instruction from the README to create it. I still think the remove will be much easier then fixing it.

@kstekovi such content at some point may go to the app development book, so IMHO for now it's important to keep it.
May I suggest to log additional JIRA(s) about that, and let @kabir check it out? We are now checking content we didn't change..

@kstekovi such content at some point may go to the app development book, so IMHO for now it's important to keep it. May I suggest to log additional JIRA(s) about that, and let @kabir check it out? We are now checking content we didn't change..

Here is the jira to track this issue. https://issues.redhat.com/browse/WFLY-21115

@kstekovi such content at some point may go to the app development book, so IMHO for now it's important to keep it. May I suggest to log additional JIRA(s) about that, and let @kabir check it out? We are now checking content we didn't change..

Here is the jira to track this issue. https://issues.redhat.com/browse/WFLY-21115

thank you, I reassigned to @kabir already

@kstekovi guess I can merge this one now and port it downstream?

@kstekovi guess I can merge this one now and port it downstream?

yes, you can merge it.