There is no end-of-life date mentioned on official documentation or website of Jakarta JSP.
The below is brief history of JSP package/api changes.
3.0.0 (namespace package was changed from this release):
- This release affected the Specification, API, TCK, and Compatible Implementations because of namespace changed
- The full description can be found in the Jakarta EE 9 Release Plan (https://eclipse.org/community/eclipse_newsletter/2020/august/1.php)
- Bundle name: Jakarata Server Pages
- Specification vendor: Eclipse Foundation
- Namespace: jakarta.servlet
- Group id: jakarta.servlet.jsp
- Artifact id: jakarta.servlet.jsp-api
- Maven repository: https://mvnrepository.com/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-api
2.3.4 (group id/artifact id were changed from this release):
- First release of the JSP API under EE4J
- Both the API and the behaviour are unchanged
- The code has been cleaned up (standard EE4J formatting applied, Javadoc errors fixed, IDE warnings (e.g. stray semi-colons) fixed, etc.
- Bundle name: JavaServer Pages
- Specification vendor: Eclipse Foundation
- Namespace: javax.servet.jsp
- Group id: jakarta.servlet.jsp
- Artifact id: jakarta.servlet.jsp-api
- Maven repository: https://mvnrepository.com/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-api
2.2.x → 2.3.3:
- Bundle name: JavaServer Pages
- Specification vendor: Oracle Corporation
- Namespace: javax.servet.jsp
- Group id: javax.servlet.jsp
- Artifact id: javax.servlet.jsp-api
- Maven repository: https://mvnrepository.com/artifact/javax.servlet.jsp/javax.servlet.jsp-api