You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.
From what I was the main license for jboss-el is LGPL-3.0, but it is strange since all the code from this package is under Apache-2.0. Can you please give more info? Did Jacob Hookom contributed this code to Seam under LGPL?
Also who created jboss-el? I have search on the internet but no luck. I would appreciate if you could give me some info.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @Alex-Vaduva,
I don't know exactly all details about Jacob's contributions, the code was commited by @orb and @pmuir who could have some agreement from Jacob Hookom or just include some classes from Jacob's work, but what is known is that Hookom's code was licensed under Apache-2.0. As whole Seam 1/2.x was licensed under LGPL and the jboss-el was work of Seam developers it was licensed also under the same license.
Jacob originally wrote jboss-el to provide some enhanced capabilities for the standard EL from the JCP. Since then all the capabilities of EL were incorporated into the updated EL spec which was released as part of the Java EE 6 releases.
A package can have a different license to code included in it, assuming that this is license compatible (Apache 2 is allowed inside LGPL packages).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From what I was the main license for jboss-el is LGPL-3.0, but it is strange since all the code from this package is under Apache-2.0. Can you please give more info? Did Jacob Hookom contributed this code to Seam under LGPL?
Also who created jboss-el? I have search on the internet but no luck. I would appreciate if you could give me some info.
Thanks!
The text was updated successfully, but these errors were encountered: