Good idea and good proposal.
Thanks!
You are talking about an Eclipse proposal based on Glassfish implementation. But the github repo is in the omnifaces organization and the java packages is also org.omnifaces.
The repo seems to have 2 years old files committed.
So I'm a bit lost to where the code actually comes from.
Two years ago I started this project, using my own code for an authorization module and code to make the project usable standalone (by e.g. Piranha Cloud, as well as Tomcat), and taking the GlassFish code for the transformation of constraints to permissions. Later I also added the GlassFish authorization module to offer some choice (it's mostly educational and not strictly needed to have two modules).
So it's a combination of my own code, and the code from GlassFish. If the proposal would be accepted, and the project graduated, the packages of the current Exousia project will not stay omnifaces of course. They would be renamed to likely org.glassfish.exousia.
As mentioned, part of the code is my own, e.g. this one:
I've marked these by "Copyright (c) ... OmniFaces".
Other parts are taken from GlassFish, most importantly the tricky transformation of constraints to permissions:
As mentioned, one of the two authorization modules (corresponding to the default Servlet/EJB collection/implies algorithm) is taken from GlassFish:
This one has an alternative that's my own code:
The original GlassFish code all has the original headers, marked by "Copyright (c) 1997, 2018 Oracle and/or its affiliates. All rights reserved."
Most of the headers are two years old, since a) some code was taken 2 years ago, but b) code that was taken more recently is also 2018, since it hasn't changed since then and the GlassFish repo still has 2018 as well. See e.g.
Hope this makes it more clear.
Kind regards,
Arjan
