vy commented on PR #3789: URL: https://github.com/apache/logging-log4j2/pull/3789#issuecomment-3053423599
> > @ashr123, no, absolutely not. They should not be used anywhere in Log4j. In `2.25.0` we put great effort into deprecating them – see [the release notes](https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-25-0-instant-format). > > This ties back to my earlier comment: [#3789 (review)](https://github.com/apache/logging-log4j2/pull/3789#pullrequestreview-2998821838) It doesn't. In its current state, deprecated formatters are an island – no programmatic connections from anywhere. We can safely delete them, yet keep the legacy formatters configuration knob functional. Not saying we should, but the current design allows this. Supporting a legacy behavior and internal classes associated with them (of which should not have been exported, but now it is too late) are two different things. In conclusion, deprecated formatters are an island, please keep it that way. -- 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
