Skip to content

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Apr 24, 2025

And mark is as deprecated.
It was causing issues with IronJacamar so we have a proof that this change is disruptive. And transactions are critical enough that we don't want to take any risks.

This is a follow-up of #47212.

And related to
quarkiverse/quarkus-ironjacamar#174.

And mark is as deprecated.
It was causing issues with IronJacamar so we have a proof that this
change is disruptive. And transactions are critical enough that we don't
want to take any risks.

This is a follow-up of quarkusio#47212.

And related to
quarkiverse/quarkus-ironjacamar#174.
@aloubyansky
Copy link
Member

Should we add QuarkusTransaction.getStatus() to 3.20?

@gsmet
Copy link
Member Author

gsmet commented Apr 24, 2025

It might make sense, yes.

@rsvoboda WDYT?

Copy link

quarkus-bot bot commented Apr 24, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f974e2c.

✅ 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.

You can consult the Develocity build scans.

@aloubyansky
Copy link
Member

Copy link
Contributor

@gastaldi gastaldi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, haven't noticed that it broke Artemis with IronJacamar. I'll change IronJacamar once the getStatus() lands in 3.20, as provided by @aloubyansky in #47528

@gastaldi gastaldi merged commit a4ea8c9 into quarkusio:main Apr 25, 2025
49 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.23 - main milestone Apr 25, 2025
@gsmet gsmet modified the milestones: 3.23 - main, 3.22.1 Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants