[jstl-dev] Should Pages, Tags and Expression Language API be released un

[Paul Nicolucci <pnicolucci@xxxxxxxxx>]

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

Tags Example: 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

However, we look to publish these artifacts using the EPL:

Pages: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

Tags: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

_expression_ Language: 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

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://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