Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jta-dev] Possible release of jakarta.transaction-api 1.3.4?

Thanks for the response, Grzegorz. I am glad to 2.0.1 looks fine. I will go ahead and close 193 (EE9) and 189 (EE8). If you end up needing something for EE8, please let us know.

On Fri, 6 May 2022 at 11:48, Grzegorz Grzybek <gr.grzybek@xxxxxxxxx> wrote:
Hello

pt., 6 maj 2022 o 12:26 Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> napisał(a):
Hi Grzegorz,

Please can I ask if this is something that you would still find useful? We do have the 2.0.1 release of the Jakarta Transactions API and that has OSGi changes in it. It is targeted for use in Jakarta EE 10 situations and uses the jakarta.transaction package - would your use case be able to use that version?

I checked https://github.com/jakartaee/transactions/pull/193 and from the OSGi point of view there are two issues:
 – if JTA API jar will have OSGi manifests (through maven-bundle-plugin configuration) it has to export "jakarta.transaction.*" packages, so #193 is not correct. It also has to import "jakarta" versions of Interceptor and CDI APIs.
 – different thing is that I don't see clear plan for OSGi to move to JakartaEE 9+ (javax → jakarta Java package, not only Maven groupId) - the problem (BIG problem) is that everything has to be done at once - in practice all usable JakartaEE APIs should be manifested in OSGi headers. Also there should be implementations (Web, Transaction, JPA, ...) moved to jakarta package and I don't think it'll happen soon...

However I checked https://repo1.maven.org/maven2/jakarta/transaction/jakarta.transaction-api/2.0.1/jakarta.transaction-api-2.0.1.pom and it simply looks fine, so #193 is actually not needed...

regards
Grzegorz Grzybek
 

Kind regards,
Tom

On Tue, 22 Jun 2021 at 12:26, Grzegorz Grzybek <gr.grzybek@xxxxxxxxx> wrote:
Hello

Some time ago I was working on JTA API issue related to OSGi[1]. The changes are already available in master branch of eclipse-ee4j/jta-api/master branch[2].

However, there's PR opened to backport the same changes to RELEASE-1.3.3 branch[3].

The changes (both in master and RELEASE-1.3.3 branches) are completely safe from the point of view of JavaEE and JTA specification, these are related only to how jakarta.transaction/jakarta.transaction-api jar is resolved as OSGi bundle.

Would it be possible to release version 1.3.4 of jakarta.transaction/jakarta.transaction-api artifact to Maven Central?

I'll be happy and honored to answer any questions regarding my PR.

kind regards
Grzegorz Grzybek
===
_______________________________________________
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

Back to the top