Re: [glassfish-dev] Splitting up the jakarta work

[Russell Gold <russell.gold@xxxxxxxxxx>]

Can this not be one, one library at a time? That is, each PR handles the changes for the library and all of its references, but no more? 

Russ

On Mar 23, 2020, at 11:29 AM, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

I recently started trying to do the work to integrate Jakarta connectors namespace change as the implementation of the api is in core GlassFish. However to do so I also had to start doing the work on Jakarta transactions. Also now I’ve hit that I also need to do all the changes for EJB as well or GlassFish won’t compile. I have a horrible suspicion that this change is likely going to suck in a lot of the apis and hit a huge chunk of the code base.

 

Does anybody have any good ideas on how to work in parallel on a lot of this work?

 

I’m starting to think that a large chunk of the work is going to have to be done in one go in one PR!

 

Does anybody have a better idea?

 

Steve

 

 

_______________________________________________
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!KCrJfd9RxFJu3Yvq84Jj8UgY83QDwEKWPYX5Hw-_GeC1B3j0wOFQUWQ7x_RKjmE-7w$