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

Provide additional safeguards when mixing RESTEasy stacks #35468

Merged
merged 1 commit into from
Aug 23, 2023

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Aug 22, 2023

Resolves: #35454

@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Aug 22, 2023
@quarkus-bot

This comment has been minimized.

@geoand
Copy link
Contributor Author

geoand commented Aug 23, 2023

I had to update the logic. It's not terribly satisfactory, but I think it covers all the cases

@geoand geoand removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Aug 23, 2023
@quarkus-bot
Copy link

quarkus-bot bot commented Aug 23, 2023

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@geoand geoand requested a review from gsmet August 23, 2023 08:48
@gsmet gsmet merged commit b5dbffc into quarkusio:main Aug 23, 2023
@quarkus-bot quarkus-bot bot added the kind/enhancement New feature or request label Aug 23, 2023
@quarkus-bot quarkus-bot bot added this to the 3.4 - main milestone Aug 23, 2023
@geoand geoand deleted the #35454 branch August 23, 2023 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rest kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Warn users if they mix RESTEasy Classic and Reactive
2 participants