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

[Russell Gold <russell.gold@xxxxxxxxxx>]

> On Jan 8, 2020, at 1:59 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
> 
> Yes, we need to do most of the work in dependency order.  The Jakarta EE 9
> release plan [1] has a set of "waves" that show the ordering.  The ORB isn't
> included and that's probably a mistake.  We would need your help to understand
> where it fits in in the dependency ordering.

orb -> orb-gmbal -> [orb-gmbal-commons, orb-gmbal-pfl]

Note: orb-gmbal-pfl contains a very old version of asm under the artifact id pfl-asm. If Glassfish is still using that, we’d want to remove it.
Currently, the ORB is built so that it should run under JDK11 (pfl-basic is an MR jar). Some additional work will be needed in Glassfish to take advantage of that.
> 
> Will any of the javax.rmi APIs need to be changed to jakarta.rmi?

How would I figure that out?

> I assume all of the RMI/IIOP APIs are actually removed from Java SE and so
> would need to be changed to jakarta.* APIs to be included in Jakarta EE 9.

There could be a fair bit, there. Not sure how you schedule my time with Tom Snyder.

- Russ
> 
> [1]
> https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan
> 
> 
> Russell Gold wrote on 1/8/20 10:43 AM:
>> Would we need to move the dependencies there first? How many of them (such as the orb) are affected?
>> 
>>> On Jan 8, 2020, at 1:30 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>>> 
>>> 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
>>