ppkarwasz commented on PR #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1195912641
@romainmoreau: I just forgot to add it, thanks for noticing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
ppkarwasz commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1082395718
@astappiev,
As far as I am concerned, this could end up in the next release. You can
check if it works for you.
--
This is an automated message from the Apache Git
ppkarwasz commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1048291947
@garydgregory: I moved the `SmtpManager` to a new `log4j-jakarta-smtp`
module.
The choice between the `javax.*` and `jakarta.*` version is automatic, based
on the
ppkarwasz commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1034024340
@jvz: is there any sense in using `javax.*` in the 3.0 release? Spring Boot
6.0 with a baseline of Java 17 and Jakarta EE 9 is due at the end of this year.
--
This is
ppkarwasz commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1033157134
@garydgregory: I think of this as a nice application of the separation
between appenders and managers, which mitigates the problems of the
jakartification.
Howeve
