[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3601: -- Fix Version/s: 2.20.0 > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Affects Versions: 2.19.0 >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.20.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. {{log4j-slf4j18-impl}} similarly had scope=runtime. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Apache Jena) use slf4j in the main code base, and select log4j > when it needed for binaries tests so we have multiple places where the > dependency happens. We can change - but this may be a user experience for > others as well. > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile > [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime > {noformat} > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3601: Affects Version/s: 2.19.0 > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Affects Versions: 2.19.0 >Reporter: Andy Seaborne >Priority: Major > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. {{log4j-slf4j18-impl}} similarly had scope=runtime. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Apache Jena) use slf4j in the main code base, and select log4j > when it needed for binaries tests so we have multiple places where the > dependency happens. We can change - but this may be a user experience for > others as well. > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile > [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime > {noformat} > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3601: Fix Version/s: (was: 2.19.0) > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. {{log4j-slf4j18-impl}} similarly had scope=runtime. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Apache Jena) use slf4j in the main code base, and select log4j > when it needed for binaries tests so we have multiple places where the > dependency happens. We can change - but this may be a user experience for > others as well. > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile > [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime > {noformat} > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. {{log4j-slf4j18-impl}} similarly had scope=runtime. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Apache Jena) use slf4j in the main code base, and select log4j when it needed for binaries tests so we have multiple places where the dependency happens. We can change - but this may be a user experience for others as well. {noformat} [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime {noformat} {noformat} [INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile [INFO] | \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile {noformat} was: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime {noformat} {noformat} {noformat} > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.19.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. {{log4j-slf4j18-impl}} similarly had scope=runtime. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Apache Jena) use slf4j in the main code base, and select log4j > when it needed for binaries tests so we have multiple places where the > dependency happens. We can change - but this may be a user experience for > others as well. > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile > [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime > {noformat} > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime {noformat} {noformat} {noformat} was: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.19.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Jena) use slf4j in the main code base and include log4j for > tests: > {noformat} > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile > [INFO] | +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile > [INFO] | \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime > {noformat} > {noformat} > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} was: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.19.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Jena) use slf4j in the main code base and include log4j for > tests: > {noformat} > {noformat} > {noformat} > [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test > [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. Example: we (Jena) use slf4j in the main code base and include log4j for tests: {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} was: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.19.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > Example: we (Jena) use slf4j in the main code base and include log4j for > tests: > {noformat} > [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test > [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test > [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test > {noformat} > {noformat} > [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test > [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test {noformat} {noformat} [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test {noformat} was: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core. The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. This changed as part of [commit 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] although it seems to be unrelated. It makes switching over more of a bump. Previously just depending on {{log4j-slf4j-impl}} was enough. Please switch back to a scope=runtime dependency. > log4j-slf4j2: change of dependency scope for log4j-core > --- > > Key: LOG4J2-3601 > URL: https://issues.apache.org/jira/browse/LOG4J2-3601 > Project: Log4j 2 > Issue Type: Improvement > Components: SLF4J Bridge >Reporter: Andy Seaborne >Priority: Major > Fix For: 2.19.0 > > > The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on > log4j-core. > The artifact {{log4j-slf4j2-impl}} has a scope=test dependency on log4j-core. > This changed as part of [commit > 8f63620875|https://github.com/apache/logging-log4j2/pull/1024/files#diff-d3ba9956a9f81420d0be3d69477a05b505746272d548ab17404aa47f3e5946b0] > although it seems to be unrelated. > It makes switching over more of a bump. Previously just depending on > {{log4j-slf4j-impl}} was enough. > Please switch back to a scope=runtime dependency for {{log4j-slf4j2-impl}}. > {noformat} > [INFO] \- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.19.0:test > [INFO]+- org.apache.logging.log4j:log4j-api:jar:2.19.0:test > [INFO]\- org.apache.logging.log4j:log4j-core:jar:2.19.0:test > {noformat} > {noformat} > [INFO] \- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:test > [INFO]\- org.apache.logging.log4j:log4j-api:jar:2.19.0:test > {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010)