Would it be sufficient to create a 3.0.1 service release for tags to expand the range for the OSGi Import for _expression_ language and pages?
Import-Package: jakarta.el;version="[5.0,6)",jakarta.servlet;version="[6.0,7)",jakarta.servlet.http;version="[6.0,7)",jakarta.servlet.jsp;version="[3.1,4)",jakarta.servlet.jsp.jstl.core,jakarta.servlet.jsp.tagext;version="[3.1,4)",javax.xml.parsers,org.xml.sax,org.xml.sax.helpers
Import-Package: jakarta.el;version="[5.0,7)",jakarta.servlet;version="[6.0,7)",jakarta.servlet.http;version="[6.0,7)",jakarta.servlet.jsp;version="[3.1,5)",jakarta.servlet.jsp.jstl.core,jakarta.servlet.jsp.tagext;version="[3.1,5)",javax.xml.parsers,org.xml.sax,org.xml.sax.helpers
WebSphere Jakarta delivery lead
-----Original Message-----
Subject: Re: [jakarta.ee-spec] [EXTERNAL] Could one of the Specification Committee members please promote the following (Jakarta EE 10) TCK service releases...
Date: 07/12/2024 05:22:50 PM
Also related to tags is JEA-242. I have not followed this closely enough to be able to easily tell if the following is done. Can someone confirm if it is? From
the above issue: Players Pages 4. 0 depends on EL 6 M1 Tags 3. 0
(JSTL) depends on
Also related to tags is
JEA-242.
I have not followed this closely enough to be able to easily tell if the following is done. Can someone confirm if it is? From the above issue:
-
Pages 4.0 depends on EL 6 M1
-
Tags 3.0 (JSTL) depends on EL 5 M1
-
We cannot have this mismatch due to OSGi.
-
Do a Tags 3.1 which increases the dependency on EL to be 6 M1.
-
This requires specification committee action to approve the release, even if the only thing changing is incrementing the EL dependency level.
-
Timeframe: target this to Milestone 2.
Bottom line: @arjan.tijms
will take the necessary actions to push this through for M1 and we will do the process work to do the right thing for M2.
Thanks,
Ed
_______________________________________________
jakarta.ee-spec mailing list