[jira] [Closed] (GERONIMO-6483) org.apache.geronimo.transaction.manager.RecoveryImpl should create slf4j logger using its own class name

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

Mark Struberg closed GERONIMO-6483.
-----------------------------------
    Resolution: Won't Fix

Closing old outdated issues.

Note that the Apache Geronimo Application Server itself was declared EOL in 2017 and we do not maintain the server parts anymore.

We still do actively maintain many of the Java EE / Jakarta EE which saw the light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please feel free to reopen the ticket.
thanks, your Apache Geronimo team!

> org.apache.geronimo.transaction.manager.RecoveryImpl should create slf4j logger using its own class name
> --------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6483
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6483
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>    Affects Versions: 3.0.1
>            Reporter: Torsten Mielke
>            Priority: Trivial
>         Attachments: GERONIMO-6483.patch
>
>
> Right now org.apache.geronimo.transaction.manager.RecoveryImpl
> sets up logging as follows
> {code:java}
> private static final Logger log = LoggerFactory.getLogger("Recovery");
> {code}
> but in order to configure logging for this class intuitively it should rather use
> {code:java}
> private static final Logger log = LoggerFactory.getLogger(RecoveryImpl.class);
> {code}
> Please get this changed.



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