[
https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517853
]
Jason Dillon commented on GERONIMO-2401:
----------------------------------------
I really think that we should really think about using slf4j instead of
commons-logging... and perhaps even change our logging instance strategy a
little.
Right now we have static loggers per class (for most things), and what I am
starting to think is that instance loggers are better, so that logging for
multiple instances of bits that are bound under different contexts can be
effectively controlled and managed better.
For example, we might want all logs for a particular application to end up in a
specific file, but none of the other bits from other apps. This isn't very
easy to do right now with the static loggers, though it can be done. I suggest
we re-think this and other logging aspects for 2.1 and make that release one
with really solid, flexible and reliable logging, which IMO is one of the most
important facilities which an application server can provide. Logging is
helpful for development, qa, staging and production, it impacts every aspect of
the life-cycle of an app deployed in an application server... and IMO we really
need to do a *much better* job in the logging scene.
> Upgrade commons-logging to 1.1
> ------------------------------
>
> Key: GERONIMO-2401
> URL: https://issues.apache.org/jira/browse/GERONIMO-2401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: dependencies, Logging
> Affects Versions: 1.2, 2.0-M5
> Reporter: Jason Dillon
> Assignee: Jason Dillon
> Fix For: 2.1
>
>
> Upgrade commons-logging to the latest release 1.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
