| Re: [jta-dev] New release for Jakarta EE 12? |
Additionally if I'm not mistaken UserTransaction still doesn't support @Inject, but needs the ancient and overloaded @Resource for injection. To align with the platform goal of moving to CDI, UserTransaction should be injectable with @Inject. At least Quarkus already supports this.
On Thu, 3 Apr 2025 at 10:58, Tom Jenkinson via jta-dev <jta-dev@xxxxxxxxxxx> wrote:To add a feature we would need to be able to provide the spec update, the API, the TCK and some proof the TCK can be passed. If we have a volunteer to provide the work and it can be reviewed by committers on the project we can include a new feature._______________________________________________On Thu, 3 Apr 2025 at 08:21, Christian Beikov via jta-dev <jta-dev@xxxxxxxxxxx> wrote:_______________________________________________Hi,
I really think that JTA.next should at provide a solution for https://github.com/jakartaee/transactions/issues/220
This is a major enabler for various optimizations as we figured out also in various Quarkus related conversations.
What does have to happen that this can be addressed?
Regards,
Christian
On 02.04.25 18:01, Tom Jenkinson via jta-dev wrote:
Hi,
Given we don't have new features completed that I could propose for release in EE12 I am planning on closing this issue with that information. However if someone feels strongly about adding a new feature into Jakarta Transactions for EE12 and thinks we have time to complete that work, then please can we discuss it here so we can try to go with a new feature release?
Thank you for any help people can provide,
Tom
On Wed, 26 Feb 2025 at 21:55, Jared Anderson via jta-dev <jta-dev@xxxxxxxxxxx> wrote:
Community members,_______________________________________________
Executive Summary
1. See issue #219.a. If you don't plan to have a new version for your specification in EE 12, just close the issue.b. If you plan to have a new version, use the issue to create a release plan by April 15, 2025.2. See this dashboard where the component release plan issues are tracked.
Details
On Monday I opened issue #219 in your repository to request your community to consider a new release of your component for Jakarta EE 12 by creating a new release plan. The issue contains a lot of details that explain what to do to create a release plan. You can use the issue to document initial thoughts and reference other issues in your repository as you work out what you want to include in a release plan.
A dashboard in GitHub was created to track the status of the release plan issues. The dashboard, located here, contains both a Board and Table view of the release plan issues. What is being asked of each community is to decide on if you plan to have a new release to be considered for EE 12 or not. If not, closing the issue will move it to the final column on the dashboard. If you are planning to have a new version of your component for EE 12, please follow the instructions in the issue by April 15, 2025 in order to get your issue moved to the second column for your mentor to look at the issue and get it ready for a plan ballot. You will see that your issue in the board includes the name of the mentor that was assigned to your component in EE 11.
Thanks,
Jared Anderson and Ed BurnsJakarta EE 12 Release Co-coordinators
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
_______________________________________________ jta-dev mailing list jta-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev