On Tue, Jun 21, 2022 at 8:11 PM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
Tbh it’s a complete mess and the code lifted into GlassFish is not clean IP. I’ve asked the foundation for advice in cleaning the IP.
I'm sorry that you feel it's a mess. I personally think the current solution is rather well done.
As I want to help out clear up any misunderstanding there might be, can you please tell me who at the foundation you are working with so we can schedule some time with you, me and said person?
Kind regards,
Arjan Tijms
I think the Omniconcurrent files have been changed since they came from Payara.
In the first commit only the files where portions copyright has been added. Specifically the concurrent-impl and concurrent-impl are straight copies. concurrent-extras is a collection of files copied from various
locations.
I can give permission to sign over the IP of the changes to Eclipse.
Alternatively, we could essentially redo Omniconcurrent in a new EE4J repo under the GlassFish project first. That would mean copying the exact same code over again to the Eclipse repo, donating that to Eclipse,
and then I can apply the same changes again, this time directly using Eclipse/EE4J.
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev