You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2025/11/11 22:02:00 UTC

[jira] [Updated] (GROOVY-11798) @Log4j2 uses Logger class from log4j-core instead of log4j-api

     [ https://issues.apache.org/jira/browse/GROOVY-11798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Milles updated GROOVY-11798:
---------------------------------
    Language: groovy

> @Log4j2 uses Logger class from log4j-core instead of log4j-api
> --------------------------------------------------------------
>
>                 Key: GROOVY-11798
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11798
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: BenS
>            Assignee: Eric Milles
>            Priority: Major
>
> The [transformation|https://github.com/apache/groovy/blob/d0540bcf352425165701eedbb02172b0bcaed7ee/src/main/java/groovy/util/logging/Log4j2.java#L80] used by the {{@Log4j2}} annotation utilizes {{org.apache.logging.log4j.core.Logger}} from the log4j-core library, which is the implementation for the logging system, when it should be using {{org.apache.logging.log4j.Logger}} from the log4j-api library, which is the interface that should be accessed by the code directly. While the current configuration does technically function, it requires the logging implementation to be available at compilation time as opposed to only at runtime as described by the [Log4j documentation|https://logging.apache.org/log4j/2.x/manual/installation.html]. Additionally, [Groovy's documentation|http://example.com/] for the annotation does not accurately reflect the transformation and indicates that it _does_ use the api's Logger.
>  
> Please let me know if any further information is required.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)