Hello!
I planned to review remaining tasks/issues in pax-web master branch (8.0.0-SNAPSHOT) and achieve OSGi R7 compatibility, but I didn't have that much time recently to do it.
Along the way, I've created
https://ops4j1.jira.com/browse/PAXWEB-1190 epic ("Improve pax-web before 8.0.0 release") with few subissues. I already cleaned up poms (added enforce-plugin to prevent using version numbers outside <dependencyManagement> for example) and I'm at the stage of reviewing pax-web-jsp.
Did you now (by the way), that ref impl (org.apache.taglibs) of JSTL got rid of "org.apache.taglibs.standard.extra.spath" package
9 years ago? It was part of some example anyway, but this package is still being used in few JSTL forks:
– org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec
– org.glassfish.web:javax.servlet.jsp.jstl
– org.glassfish.web:jakarta.servlet.jsp.jstl (!)
Anyway - I want 8.0.0 to be nicely OSGi R7 compliant (but there are still some things to improve wrt R6 Whiteboard spec). So I'm going to release pax-web-7.3.0 without R7 compatibility (osgi.jaxrs), but with Tomcat 9 and Undertow 2 support.
We could treat it as tech preview and possibly detect some issues with this approach. Jetty 10 (Servlet API 4) isn't ready (AFAIK) yet anyway...
What do you think?
regards
Grzegorz Grzybek