Log4j pollutes downstream compile classpaths, for example making compilation slower

Abierto
  • ¿Algo no está bien?
#4,034 9 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@ppkarwasz ya está trabajando en esto.

Desde el 16/3/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug build dependencies priority: P2

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+

Lenguaje dominante
Java
Estrellas
3.6k
Forks
1.8k
Merge medio
5 d 6 h
PR fusionados (30 d)
24

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/logging-log4j2

Todos los issues de apache/logging-log4j2

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.