ppkarwasz commented on issue #3401:
URL:
https://github.com/apache/logging-log4j2/issues/3401#issuecomment-2599053582
> I'm trying to port a project using JSP from Tomcat 9 to Tomcat 10.1.34 but
"Apache Log4j Tag Library" ("log4j-taglib-2.24.3.jar")
is not working anymore.
The `log4j-taglib` artifact only supports JavaServer Pages 2.3 (part of Java
EE 8) or earlier releases. As you are probably aware, Jakarta Server Pages 3.0
and later (part of Jakarta EE 9) uses a new `jakarta.*` namespace for classes,
instead of the `javax.*` namespace, which is a breaking change. Currently we
don't plan any version of `log4j-taglib` compatible with JSP 3.0 (see
[documentation](https://logging.apache.org/log4j/2.x/jakarta.html#log4j-taglib))
and the `log4j-taglib` artifact is scheduled for removal in Log4j Core 3.
Could you tell us more about your application? Are you still using
`log4j-taglib` in production? There are multiple reasons for the deprecation:
- according to our download statistics, the `log4j-taglib` artifact is
barely used.
- most of the tools we used to generate the artifact (e.g.
`taglib-maven-plugin`) have gone EOL.
- since modern JSP pages are only used as HTML templates and don't contain
Java code any more, we believe that the need for logging in a JSP page has
disappeared.
- Apache Log4j has a lot of components and we don't have enough time to
ensure that all the components are high quality. In particular `log4j-taglib`
needs some love.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
