Log4j pollutes downstream compile classpaths, for example making compilation slower
维护者通常 1 天内回复
@ppkarwasz 已经在做这个了。
开始于 2026年3月16日。
评估
这个 Issue 还没有评估数据。
描述
Description
Log4j since version 2.25 publishes Gradle Module Metadata.
In the Gradle Module Metadata it declares dependencies on 5 libraries that only contain annotations and that are only used to annotate code, not anywhere in the API.
These dependencies should not be exposed in the apiElements variant as that just pollutes the downstream compile classpaths.
Annotations for which no classfile is present are ignored by the JVM.
If someone wants to use those annotations, that someone is responsible to add the annotation to the classpath.
If this was added to work-around the problem that you get a warning (and with -Werror an error) from the Java compiler about missing class files for enum constants used in annotations, this is a bug in the Java compiler (https://bugs.openjdk.org/browse/JDK-8305250) and should imho not be worked-around on the library-level.
As you can for example read at https://mail.openjdk.org/pipermail/jdk-dev/2024-October/009459.html and https://bugs.openjdk.org/browse/JDK-6322301, annotations for which no classfile is present should be ignored by the JVM.
This should be fixed by fixing the bug in javac.
As work-around on the client side, one could stop using -Werror, disable that specific linting option, or add the dependencies in question to the compileOnly configuration.
It is imho not the responsibility of a library to work-around this bug in Javac that is used by downstream projects with special configuration, thereby polluting the compile classpath of all downstream projects even if they don't use that option that makes the warning an error and thus making compilation slower for all downstream projects unless they then manually exclude those dependencies.
Configuration
Version: 2.25+
- 主要语言
- Java
- 星标
- 3.6k
- 派生
- 1.8k
- 平均合并
- 5 天 6 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/logging-log4j2 的其他 Issue
-
waiting-for-maintainer
难度 2/5 1-3 小时 新手友好度 63/100
apache/logging-log4j2#4475 ·
维护者通常 1 天内回复
-
Migrate `log4j-api-test` tests to JUnit 5可能重新可做 关联的 PR 已关闭且未合并。 未关闭api priority: P3 tests waiting-for-maintainer
难度 2/5 1-3 小时 新手友好度 68/100
apache/logging-log4j2#4430 · 1 条评论 ·
维护者通常 1 天内回复
-
`Rfc5424Layout` does not escape the `newLineEscape` replacement in SD-PARAM-VALUE可能已有人在做 @lunarbae628 于 6 天前认领。 未关闭bug layouts priority: P3
apache/logging-log4j2#4464 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
configuration enhancement layouts
难度 4/5 3-5 天 新手友好度 55/100
apache/logging-log4j2#4463 ·
维护者通常 1 天内回复
-
`evaluateOnStartup="true"` saves logs under wrong file names after missing scheduled roll可能重新可做 关联的 PR 已关闭且未合并。 未关闭appenders:Rolling bug priority: P1 waiting-for-maintainer
难度 3/5 1-2 天 新手友好度 30/100
apache/logging-log4j2#4449 ·
维护者通常 1 天内回复
查看 apache/logging-log4j2 的全部 Issue
相似的 Issue
-
[FEATURE] Expose external refresh, node-level translog and warmer stats可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭untriaged
难度 2/5 1-3 小时 新手友好度 68/100
opensearch-project/opensearch-prometheus-exporter#680 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 78/100
-
Good First Issue
难度 1/5 1-3 小时 新手友好度 88/100
hiero-ledger/hiero-sdk-java#3059 ·
维护者通常 1 天内回复