For JPA, I’d imagine that the JDBC appenders are better suited. On the other 
hand, JDBC is still part of standard Java while JPA is technically an Eclipse 
thing now (Jakarta).

On Sep 12, 2023, at 3:42 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:

Hey Piotr,

[My answers are inline.]

On Mon, Sep 11, 2023 at 1:10 PM Piotr P. Karwasz <piotr.karw...@gmail.com>
wrote:

What about `kubernetes`, `docker` and `jpa`. Are these omissions
intentional?


They can indeed be gone too. In the context of `kubernetes` and `docker`,
similar to Matt, my experience has always been in the direction that these
properties are exported to environment variables. For `jpa`, I don't have
much experience, hence my reluctance. But if you'd ask me, we should get
rid of that too.


Our employers are the Open Source equivalent of paying customers. If I
am not mistaken they allowed you to work on Log4j at one time or
another.
When Gary says "please don't drop..." I take it as a declaration that
he'll handle the issues filed against these modules (and he does do
it).


I think that is a slippery slope to base the decision of whether we shall
keep a functionality or not. If my employer would be using
`formatMsgNoLookups`, and I volunteer to maintain it even after Log4Shell,
shall we still keep it around? We shouldn't keep a feature because somebody
is paid to maintain it. It should make sense to distribute it with the
official product. Though note that the paid maintainers can still develop
that feature in a separate non-ASF GitHub repository.

Reply via email to