On Wed, Jun 8, 2022 at 12:35 PM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
We will look internally to see how long it would take us to backport Payara changes upstream to GlassFish.
Maybe that's not even needed, although it would of course be much appreciated ;)
As I’ve also said before there’s no guarantee that the work is trivial.
I agree; basically what would be enough is for Payara to give a blanket permission to copy bits and pieces of the integration code if and where needed, and commit those to GlassFish under the Eclipse Public License v. 2.0, and secondary GNU General Public License, version 2 with the GNU Classpath Exception. Maybe during that process we discover that GlassFish and Payara have diverged too much already for any direct copying, but it would be good to have initial permission.
IMHO it would be simpler just to reimplement the glue code and support for the concurrency deployment annotations in the GlassFIsh
project. We have already completed and pushed upstream the whole of the Concurrency RI project work.
That's certainly very much appreciated, thanks for that Steve!
I think Payara and the GlassFish team have cooperated very well on EE 10, with Payara doing the Concurrency RI project work, and us doing the Mojarra, WaSP and Exousia work. We even worked on Soteria directly together with Payara contributing the initial code, and where we integrated it more deeply in Soteria and did the TCK for it.
Kind regards,
Arjan Tijms
