Re: [glassfish-dev] GlassFish updates for the javax -> jakarta transitio

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Steve Millidge (Payara) wrote on 1/9/20 2:49 AM:
> My preference would be to switch master to 6.x and create a maintenance branch off the 5.1.0 tag.

I agree.  Do we need to start collecting +1's?  :-)

> On the list of things to do it looks reasonable but won't know for sure until a first pass through it.

Yes, I'm sure there's at least a few things that are missing.

> One other thing is whether we remove the support for the removed apis.

We can't remove support for any optional APIs since we still need a Compatible
Implementation that supports them all.

Separately we need to decide what level of backwards compatibility support
Eclipse GlassFish will offer.  I'm still hoping that someone will create a
backwards compatibility project that can be shared by multiple Jakarta EE
implementations.  It would be useful to prototype such a project in GlassFish.

Even ignoring backwards compatibility, my understanding is that the platform
TCK depends heavily on the Deployment API, so if we remove that we're going to
have to figure out what to replace it with.


What's you're feeling on the "javax -> jakarta" work vs. the JDK 11 work?
How do we coordinate them?


> Steve
> 
> 
> -----Original Message-----
> From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Bill Shannon
> Sent: 08 January 2020 18:31
> To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
> Subject: [glassfish-dev] GlassFish updates for the javax -> jakarta transition
> 
> Do we have a plan for how to manage the GlassFish project as some of the APIs start the transition from javax to jakarta?
> 
> (Note that I asked the same question of the TCK project; it would be nice to use the same conventions there and here and coordinate the work.
> 
> Should these contributions be made in a new "6.0.0" branch?
> 
> Is it time to convert the master branch to "6.0.0-SNAPSHOT" and move any 5.x maintenance to a separate maintenance branch?
> 
> Presumably any update to the API to move to the jakarta namespace should include
> 
> - update of the API jar file dependency
> - update of the implementation (included, or dependency)
> - update of any usage on the APIs in other GlassFish code, e.g., admin console
> - update of any tests in the GlassFish repository
>   (are all tests still valid, functional, and regularly executed?)
> - update of any documentation that uses the APIs, e.g., in examples
> - update of any CI tests that depend on the API or jar file names
> - update of the API jar files in the jakartaee-api project
> - anything I forgot?
> _______________________________________________
> glassfish-dev mailing list
> glassfish-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
> _______________________________________________
> glassfish-dev mailing list
> glassfish-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/glassfish-dev
>