[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
 | 
Steve,
Thank you for being so helpful and responsive. Hopefully, this situation 
was exclusive for Jakarta EE 9 and the big bang move.
Jersey 3.0.0 is in central, GlassFish 6.0.0 final is good to go.
Happy Jakarta,
Jan
On 03.12.2020 10:38, Steve Millidge (Payara) wrote:
So question is are we still OK to release these components as final 
versions included by GlassFish 6.0.0 final and still reference Jersey 
3.0.0?
Steve
*From:*glassfish-dev-bounces@xxxxxxxxxxx 
<glassfish-dev-bounces@xxxxxxxxxxx> *On Behalf Of *Steve Millidge (Payara)
*Sent:* 03 December 2020 09:36
*To:* glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
*Subject:* Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
OK Corba 4.2.3-RC2 is in maven central
*From:*glassfish-dev-bounces@xxxxxxxxxxx 
<mailto:glassfish-dev-bounces@xxxxxxxxxxx> 
<glassfish-dev-bounces@xxxxxxxxxxx 
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>> *On Behalf Of *Steve 
Millidge (Payara)
*Sent:* 03 December 2020 09:25
*To:* glassfish developer discussions <glassfish-dev@xxxxxxxxxxx 
<mailto:glassfish-dev@xxxxxxxxxxx>>
*Subject:* Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
OK Shoal 2.0.0-RC1 has been released. I will work on CORBA today.
Steve
*From:*glassfish-dev-bounces@xxxxxxxxxxx 
<mailto:glassfish-dev-bounces@xxxxxxxxxxx> 
<glassfish-dev-bounces@xxxxxxxxxxx 
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>> *On Behalf Of *Maxim Nesen
*Sent:* 03 December 2020 07:20
*To:* glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
*Subject:* Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
Hi,
I doubt that this solution can be applied to Jersey 3.0.0 (which is 
already in staging waiting to be promoted to central) without changes 
inside Jersey. As a result this will lead to re-spin of Jersey 3.0.0 
(which is not preferable), or publishing of version 3.0.1 (but then 
version 3.0.0 will not be in central), so I would go that way only if 
there are some serious obstacles which prevent Corba 4.2.3-RC2 and 
Shoal 2.0.0-RC1 from being promoted to Central. Technically it's much 
easier to promote those 2 artifacts to Central. But I do not know, if 
anything blocks this...
Regards,
Maxim
----- Original Message -----
From: arjan.tijms@xxxxxxxxx <mailto:arjan.tijms@xxxxxxxxx>
To: glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
Sent: Thursday, December 3, 2020 7:44:21 AM GMT +01:00 Amsterdam / 
Berlin / Bern / Rome / Stockholm / Vienna
Subject: 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 
<mailto: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@xxxxxxxxx <mailto:arjan.tijms@xxxxxxxxx>
    To: glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
    Sent: 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,
    On Thu, Dec 3, 2020 at 1:20 AM Jan Supol <jan.supol@xxxxxxxxxx
    <mailto:jan.supol@xxxxxxxxxx>> wrote:
        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
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visithttps://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/glassfish-dev__;!!GqivPVa7Brio!OQF9KECA5uHAz70Nl5QnwXvachk1K60q8egTt9w2w4-XmEoBDyyGMTARmyVNZM7B$