[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [glassfish-dev] org.glassfish.corba:4.2.3-RC2
|
On 12/3/20 4:33 PM, arjan tijms wrote:
Hi,
Good that it works now!
Jan, is GF broken by design regarding that dependency, or was it
something specifically in those RC builds?
It's more likely caused by previous evolution of particular
implementations as they wanted to provide better integration with the
server. Say for feature X they required some change in the GF internal
API so they could use it, gf published this new - not necessarily
internal - API through some M/Beta/RC build so the implementation can
use it (speaking maven "under provided scope") and as long as such API
does not change, everything is fine but the cycle is evident.
..hm, does this make sense?
Can we prevent this in the future somehow?
the only way to prevent this would be to disallow implementations to use
newly introduced server APIs. But I'm pretty sure one could come up with
some process for this, once it's needed.
thanks,
--lukas
Thanks!
On Thursday, December 3, 2020, Steve Millidge (Payara)
<steve.millidge@xxxxxxxxxxx> wrote:
Thanks for your work Jan.
The big bang move does have a lot of inter-dependencies many of
which we don't control so it is complex. I think we have a whole
bunch of other dependencies to go final before we can go final.
Steve
-----Original Message-----
From: glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>
<glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>> On Behalf Of Jan Supol
Sent: 03 December 2020 14:29
To: glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
Subject: 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
<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:36
> *To:* glassfish developer discussions <glassfish-dev@xxxxxxxxxxx
<mailto: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>
> <mailto:glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>>
> <glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>
> <mailto: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>
> <mailto: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>
> <mailto:glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>>
> <glassfish-dev-bounces@xxxxxxxxxxx
<mailto:glassfish-dev-bounces@xxxxxxxxxxx>
> <mailto: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> <mailto: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>
<mailto:arjan.tijms@xxxxxxxxx <mailto:arjan.tijms@xxxxxxxxx>>
> To: glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
<mailto: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>
> <mailto: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>
<mailto:arjan.tijms@xxxxxxxxx <mailto:arjan.tijms@xxxxxxxxx>>
> To: glassfish-dev@xxxxxxxxxxx
<mailto:glassfish-dev@xxxxxxxxxxx> <mailto: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>
> <mailto: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 <mailto:glassfish-dev@xxxxxxxxxxx>
> To unsubscribe from this list,
>
visithttps://urldefense.com/v3/__https://www.eclipse.org/mailman/listi
<http://urldefense.com/v3/__https://www.eclipse.org/mailman/listi>
>
nfo/glassfish-dev__;!!GqivPVa7Brio!OQF9KECA5uHAz70Nl5QnwXvachk1K60q8eg
> Tt9w2w4-XmEoBDyyGMTARmyVNZM7B$
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/glassfish-dev__;!!GqivPVa7Brio!NDxVVQE_NCHIBW7FFOsrdeZfSzNrNcDaoomOrYzuaiMV6JTcbe59BLfU6pwbdyLKa9I$>
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/glassfish-dev__;!!GqivPVa7Brio!NDxVVQE_NCHIBW7FFOsrdeZfSzNrNcDaoomOrYzuaiMV6JTcbe59BLfU6pwbdyLKa9I$>
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/glassfish-dev__;!!GqivPVa7Brio!NDxVVQE_NCHIBW7FFOsrdeZfSzNrNcDaoomOrYzuaiMV6JTcbe59BLfU6pwbdyLKa9I$
