[
https://issues.apache.org/jira/browse/GROOVY-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072851#comment-18072851
]
ASF GitHub Bot commented on GROOVY-11922:
-----------------------------------------
paulk-asert commented on code in PR #2461:
URL: https://github.com/apache/groovy/pull/2461#discussion_r3067977716
##########
subprojects/groovy-servlet/src/spec/doc/servlet-userguide.adoc:
##########
@@ -29,7 +29,7 @@ rather than Java code.
* An `AbstractHttpServlet` class for defining traditional Servlets.
* Helper classes like `ServletBinding` and `ServletCategory` which let you
access some of the features offered by the `groovy-servlet` module in
additional contexts.
-From Groovy 5, `groovy-servlet` supports Jakarta EE Servlet specifications.
Javax EE servlet specifications are supported in version before Groovy 5 or
with Groovy 5 by using the `javax` classifier when specifying your dependency.
+From Groovy 6, `groovy-servlet` targets Jakarta EE 11 (Servlet 6.1). It
remains compatible with Jakarta EE 10 (Servlet 6.0) containers. The `javax`
classifier is available for pre-Jakarta containers (e.g. Tomcat 9, Jetty 9).
Review Comment:
The Groovy functionality doesn't (currently) use any 6.1 exclusive
functionality but you are correct that if user code calls such things, they
will have to understand which versions they are running on. I was planning to
add some notes about that in the release notes but you are correct that
something should be here as well.
> Jakarta EE 11 compatibility for groovy-servlet
> ----------------------------------------------
>
> Key: GROOVY-11922
> URL: https://issues.apache.org/jira/browse/GROOVY-11922
> Project: Groovy
> Issue Type: Improvement
> Affects Versions: 5.0.5
> Reporter: Oleg K.
> Assignee: Paul King
> Priority: Major
> Fix For: 6.0.0-alpha-1
>
>
> Same as GROOVY-1190 but for EE11
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
