[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
|
Hi,
It should technically be possible to just publish the 6.0.0 version of GlassFish’ EJB module first, then have Jersey depend on this 6.0.0 version, publish Jersey, have GF depend on that, then publish the rest of GF 6.0.0.
On Thursday, December 3, 2020, Maxim Nesen <
maxim.nesen@xxxxxxxxxx> wrote:
Hi,
Yes sure, but any way it's required to be in Central because otherwise the final version of Jersey won't be published.
Regards,
Maxim
----- Original Message -----
From:
arjan.tijms@xxxxxxxxxTo:
glassfish-dev@xxxxxxxxxxxSent: Thursday, December 3, 2020 1:50:34 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
Hi,
org.glassfish.main.ejb:ejb-container:jar:6.0.0-RC1:provided
+- org.glassfish.main.orb:orb-connector:jar:6.0.0-RC1:provided
| +- org.glassfish.corba:glassfish-corba-omgapi:jar:4.2.3-RC2:provided
| \-
org.glassfish.corba:glassfish-corba-internal-api:jar:4.2.3-RC2:provided
+- org.glassfish.ha:ha-api:jar:3.1.12:provided
| \- org.glassfish.main.cluster:gms-bootstrap:jar:6.0.0-RC1:provided
| \- org.glassfish.shoal:shoal-gms-api:jar:2.0.0-RC1:provided
Jersey is directly using just org.glassfish.main.ejb:ejb-container.
That looks like another one of those nasty circular dependencies. GlassFish depends on Jersey, but Jersey depends on GlassFish :O
Kind regards,
Arjan Tijms