[
https://issues.apache.org/jira/browse/LOG4J2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361209#comment-17361209
]
Denis Orlov commented on LOG4J2-2816:
-
[~rpopma] lets merge and release that PR with
rgoers commented on pull request #503:
URL: https://github.com/apache/logging-log4j2/pull/503#issuecomment-858745835
I don't necessarily object to Log4j providing integrations with third party
components. But if something like liquibase chooses to provide its own logging
API then it should
nvoxland commented on pull request #503:
URL: https://github.com/apache/logging-log4j2/pull/503#issuecomment-858686682
Yes, I will keep the rest of the team up on this discussion.
I think that making log4j-api a required part of our API or standard logging
implementation is a no-go.
vy commented on pull request #503:
URL: https://github.com/apache/logging-log4j2/pull/503#issuecomment-858579063
I perfectly understand your conservative attitude for adding dependencies to
your project and share them. This said, dependencies increase re-usability and
independent evolution
