Re: [el-dev] Should Pages, Tags and Expression Language API be released

[Mark Thomas <markt@xxxxxxxxxx>]

Cross-posting but I suspect some lists will reject this as I'm not 
subscribed. Paul, feel free to forward this to those lists if you wish.

Hi,

The files for those specs have all, at some point in their history, been 
part of an Apache Software Foundation project - hence the ALv2 license 
on some - but not all - of the files for those projects.

When Sun/Oracle (I forget which it was) forked those projects to create 
Glassfish the ALv2 license had to be retained for the existing files. 
New files were created with a different license. When the projects were 
donated to Eclipse, the license for those new files was changed to 
"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0" (because Oracle owned 
the copyright for the new files). In Jakarta, all new files continue to 
be created with this license.

We can't release the projects as ALv2 because the "EPL-2.0 OR GPL-2.0 
WITH Classpath-exception-2.0" licensed files are not compatible with an 
overall release under ALv2.

We can continue to release the projects as "EPL-2.0 OR GPL-2.0 WITH 
Classpath-exception-2.0" because the ALv2 licensed files are compatible 
with an overall release under that license.

I'll accept that interpretation of licenses and "compatibility" between 
them is a complex topic. I am basing the above on ASF policy since the 
ASF is best placed to know the intent of the ALv2.

In short, I think we should retain the status quo.

Mark


On 17/11/2021 01:22, Paul Nicolucci wrote:
> Hi,
>
> I was looking over the Jakarta Pages,Tags, Expression Language APIs and 
> I noticed the source files have the Apache 2.0 license:
>
> Pages Example: 
> https://github.com/eclipse-ee4j/jsp-api/blob/master/api/src/main/java/jakarta/servlet/jsp/ErrorData.java 
> <https://github.com/eclipse-ee4j/jsp-api/blob/master/api/src/main/java/jakarta/servlet/jsp/ErrorData.java>
>
> Tags Example: 
> https://github.com/eclipse-ee4j/jstl-api/blob/master/api/src/main/java/jakarta/servlet/jsp/jstl/core/ConditionalTagSupport.java 
> <https://github.com/eclipse-ee4j/jstl-api/blob/master/api/src/main/java/jakarta/servlet/jsp/jstl/core/ConditionalTagSupport.java>
>
> Expression Language Example: 
> https://github.com/eclipse-ee4j/el-ri/blob/master/api/src/main/java/jakarta/el/ArrayELResolver.java 
> <https://github.com/eclipse-ee4j/el-ri/blob/master/api/src/main/java/jakarta/el/ArrayELResolver.java> 
>
>
> However, we look to publish these artifacts using the EPL:
>
> Pages:https://github.com/eclipse-ee4j/jsp-api/blob/master/LICENSE.md 
> <https://github.com/eclipse-ee4j/jsp-api/blob/master/LICENSE.md> / 
> https://search.maven.org/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-api/3.0.0/jar 
> <https://search.maven.org/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-api/3.0.0/jar>
>
> Tags:https://github.com/eclipse-ee4j/jstl-api/blob/master/LICENSE.md 
> <https://github.com/eclipse-ee4j/jstl-api/blob/master/LICENSE.md> / 
> https://search.maven.org/artifact/jakarta.servlet.jsp.jstl/jakarta.servlet.jsp.jstl-api/2.0.0/jar 
> <https://search.maven.org/artifact/jakarta.servlet.jsp.jstl/jakarta.servlet.jsp.jstl-api/2.0.0/jar>
>
> Expression Language: 
> https://github.com/eclipse-ee4j/el-ri/blob/master/LICENSE.md 
> <https://github.com/eclipse-ee4j/el-ri/blob/master/LICENSE.md> / 
> https://search.maven.org/artifact/jakarta.el/jakarta.el-api/4.0.0/jar 
> <https://search.maven.org/artifact/jakarta.el/jakarta.el-api/4.0.0/jar>
>
> Should we change these projects to publish using the Apache 2.0 License? 
> It looks like Jakarta Validation for example does that:
>
> https://github.com/eclipse-ee4j/beanvalidation-api/blob/master/license.txt 
> <https://github.com/eclipse-ee4j/beanvalidation-api/blob/master/license.txt> 
> / 
> https://search.maven.org/artifact/jakarta.validation/jakarta.validation-api/3.0.0/jar 
> <https://search.maven.org/artifact/jakarta.validation/jakarta.validation-api/3.0.0/jar>
>
> I just wanted to open this up for discussion so we can make changes to 
> Jakarta EE10 if necessary.
>
> Thanks,
>
> Paul Nicolucci
>
> _______________________________________________
> el-dev mailing list
> el-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/el-dev