[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17607371#comment-17607371
]
Andy Seaborne edited comment on LOG4J2-3601 at 9/22/22 9:31 AM:
We have the internal (clean separation of api, core and impl) and external
(user expectation of an implementation of slf4j using log4j).
The page [https://logging.apache.org/log4j/2.x/log4j-slf4j2-impl/index.html]
does not mention log4j-core. It does refer to "the log4j jars".
Links from the requirements section on that page go to:
[https://logging.apache.org/log4j/2.x/runtime-dependencies.html]
which gets you to
[https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/dependencies.html#Dependency_Tree]
(there is no slf4j2 link) where log4j-core is a runtime dependency.
So there is a history of users (if they read the documentation :)) having a
single dependency way to use log4j to provide the logging for slf4j.
With scope=runtime, there is the same degree of compile separation from
log4j-core as scope=test . It will be safe for users of log4j to exclude
log4j-core.
was (Author: andy.seaborne):
We have the internal (clean separation of api, core and impl) and external
(user expectation of an implementation of slf4j using log4j).
The page [https://logging.apache.org/log4j/2.x/log4j-slf4j2-impl/index.html]
does not mention log4j-core. It does refer to "the log4j jars".
Links from the requirements section on that page go to:
[https://logging.apache.org/log4j/2.x/runtime-dependencies.html]
which gets you to
[https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/dependencies.html#Dependency_Tree]
(there is no slf4j2 link) where log4j-core is a runtime dependency.
So there is a history of users (if they read the documentation :)) having a
single dependency way to use log4j to provide the logging for slf4j.
With scope=runtime, there is the same degree of compile separation from
log4j-core as scope=test. Exclusion of log4j-core will work.
> 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] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17607371#comment-17607371
]
Andy Seaborne edited comment on LOG4J2-3601 at 9/20/22 7:18 PM:
We have the internal (clean separation of api, core and impl) and external
(user expectation of an implementation of slf4j using log4j).
The page [https://logging.apache.org/log4j/2.x/log4j-slf4j2-impl/index.html]
does not mention log4j-core. It does refer to "the log4j jars".
Links from the requirements section on that page go to:
[https://logging.apache.org/log4j/2.x/runtime-dependencies.html]
which gets you to
[https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/dependencies.html#Dependency_Tree]
(there is no slf4j2 link) where log4j-core is a runtime dependency.
So there is a history of users (if they read the documentation :)) having a
single dependency way to use log4j to provide the logging for slf4j.
With scope=runtime, there is the same degree of compile separation from
log4j-core as scope=test. Exclusion of log4j-core will work.
was (Author: andy.seaborne):
We have the internal (clean separation of api, core and impl) and external
(user expectation of an implementation of slf4j using log4j).
The page [https://logging.apache.org/log4j/2.x/log4j-slf4j2-impl/index.html]
does not mention log4j-core. It does refer to "the log4j jars".
Links from the requirements section on that page go to:
[https://logging.apache.org/log4j/2.x/runtime-dependencies.html]
which gets you to
[https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/dependencies.html#Dependency_Tree]
(there is no slf4j2 link) where log4j-core is a runtime dependency.
So there is a history of users (if they read the documentation :)) having a
single dependency way to use log4j to provide the logging for slf4j.
With scope=runtime, there is the same degree of compile separation from
log4j-core as scope=test.
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=17607371#comment-17607371
]
Andy Seaborne commented on LOG4J2-3601:
---
We have the internal (clean separation of api, core and impl) and external
(user expectation of an implementation of slf4j using log4j).
The page [https://logging.apache.org/log4j/2.x/log4j-slf4j2-impl/index.html]
does not mention log4j-core. It does refer to "the log4j jars".
Links from the requirements section on that page go to:
[https://logging.apache.org/log4j/2.x/runtime-dependencies.html]
which gets you to
[https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/dependencies.html#Dependency_Tree]
(there is no slf4j2 link) where log4j-core is a runtime dependency.
So there is a history of users (if they read the documentation :)) having a
single dependency way to use log4j to provide the logging for slf4j.
With scope=runtime, there is the same degree of compile separation from
log4j-core as scope=test.
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=17607206#comment-17607206
]
Andy Seaborne commented on LOG4J2-3601:
---
Hi [~pkarwasz],
One of the things Jena provides is a code library so this report is a proxy for
our downstream users who may encounter the situation when going
{{log4j-slf4j-impl}} to {{log4j-slf4j2-impl}}. Our user are interested in data,
and software development is often not their main focus. We also have to
consider how our users upgrade and how we let them know what's happening.
An optional dependency doesn't change the situation. The dependency would have
to be added unlike with the current {{log4j-slf4j-impl}}. Different consistency!
For the Jena binary products that are self contained (the RDF server, and the
command line tools), we add {{log4j-core}}. Its the library usage that exposes
the change.
> 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
]
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)
[jira] [Created] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core
Andy Seaborne created LOG4J2-3601:
-
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (LOG4J2-673) plugin preloading fails in shaded jar files
[ https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113916#comment-17113916 ] Andy Seaborne commented on LOG4J2-673: -- In case it helps anyone coming to this ticket: When there is a dependency on log4j-web, there are two Log4j2Plugins.dat files to be merged in order to shade. > plugin preloading fails in shaded jar files > --- > > Key: LOG4J2-673 > URL: https://issues.apache.org/jira/browse/LOG4J2-673 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.0-rc2, 2.1 >Reporter: Michael Semb Wever >Assignee: Matt Sicker >Priority: Critical > Labels: annotations, compiler, plugins > Fix For: 3.0.0 > > Attachments: > 0002-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch, > 0005-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch > > > Support for plugin preloading through the standard > javax.annotation.processing tool was adding in LOG4J2-595 > But the plugin processor always creates and stores the processed "Plugin" > annotated classes into the same file. This works fine when the classpath > consists of individual jar files, but fails when shaded jar files are used. > A tested fix exists at > https://github.com/finn-no/logging-log4j2/tree/bugfix/LOG4J2-673 > There's also a github pull request and a manual diff attached. (I can clean > up anything not used afterwards) > The fix saves the dat file in a location under META-INF that matches the > shared package all the processed plugins are found under. > The package attribute in the config file is then used so that multiple dat > files can be loaded at runtime. > This means that the package attribute is no longer deprecated. > This has been tested against > https://github.com/finn-no/log4j2-logstash-jsonevent-layout -- This message was sent by Atlassian Jira (v8.3.4#803005)
