Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [jakartaee-platform-dev] Dependency Analysis with jQA - Cyclic Dependency in all Platform Profiles!

Thanks, Matej.

I was not expecting to provide a major upgrade of Jakarta Transactions in order to upgrade it's dependencies (and requiring JDK 11, assuming that was then necessary) but if that is required we can add the requirement to the Jakarta Transactions project.

I will mention that the Jakarta Transactions 2.0.1 version of the API passed TCK with Glassfish and using JDK 11 in:


On Mon, 16 May 2022 at 10:56, Matej Novotny <manovotn@xxxxxxxxxx> wrote:
I thought it was given that each spec included in EE 10 will have a major release, if only to upgrade dependency and JDK versions. But I might be mistaken there.

Technically, all the bits and pieces you use are still in the API under the same packages *and* you have it as provided, so you shouldn't need to upgrade.
As for JDK version, Jakarta EE 10 is aimed at JDK 11 and higher overall so all parts need to support that (not sure if 17 too on paper but it'd definitely be nice). If you update any deps, take into consideration that those will cause troubles under JDK 8 as they are mostly compiled against 11 (CDI is one of them).
Other than that, it should be fine.


On Mon, May 16, 2022 at 11:23 AM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
For EE 10, the Jakarta Tansactions project was not updated much beyond the EE9 version except some minor changes that went into a service release so there is no new major version planned for EE 10. That said, I don't understand why the Jakarta Transactions API is required to upgrade it's the CDI dependency (nor why compiling with JDK 8 is a problem, unless it would be a problem if we did need to upgrade CDI dependency).

At the Java level, Jakarta Transactions dependencies are: jakarta.enterprise.context.NormalScope [1], jakarta.enterprise.util.Nonbinding [2] [3] and jakarta.interceptor.InterceptorBinding [3]. These APIs still exist [5] [6] [7] but does the Jakarta Transactions inclusion of older API versions cause some problem?

On Mon, 16 May 2022 at 06:39, Matej Novotny <manovotn@xxxxxxxxxx> wrote:
Hmm, I was under the assumption that the tx version in CDI was the new one for EE 10 but apparently there has been no major so far (wasn't that mandatory?).

The dep was in place for years now and it wasn't an issue but I understand that cyclic dep is not nice.

I'll send a PR for removal of that dependency but it might hang in there until Tue since that's the CDI mtg day and it might get some attention there.


On Sat, May 14, 2022 at 5:31 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

On Sat, May 14, 2022 at 2:07 PM Jan Westerkamp <jan.westerkamp@xxxxxxx> wrote:
Hi Tom,

I agree - Transactions has CDI as valid dependency (right direction, higher level to lower), the core problem is the required dependency of CDI to an already outdated version of Transactions - for documentation reasons only.

Maybe we can ask Matej & Ladislav (cc'ed) to remove this?

Kind regards,
Arjan Tijms


Back to the top