Motivation: |
|
|---|---|
Contact: |
|
Tracker: |
http://jira.codehaus.org/browse/GEOT-XXXX |
Tagline: |
Use commons logging across the board |
This page represents a counter proposal to Allow redirection to alternate logging API.
Description
The use of java logging hampers our ability to work in several environments; most notably application containers. The defacto standard in this case is for libraries to use the commons-logging API; which allows
for integration with several logging frameworks.
Status
|
This proposal is under construction. Voting has not started yet: |
dynamictasklist: task list macros declared inside wiki-markup macros are not supported |
Tasks
This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success
|
no progress |
|
done |
|
impeded |
|
lack mandate/funds/time |
|
volunteer needed |
|---|
- depend on commons logging
- API changed based on BEFORE / AFTER
- Deprecate CommonLogger and Logging methods associated to it!
- Update developers guide
API Changes
BEFORE
This is a change in dependency only, as such it will effect client projects pom.xml.
AFTER
Documentation Changes
Labels
1 Comment
Hide/Show CommentsOct 30, 2007
Martin Desruisseaux
Just a reminder: Commons-Logging is reputed to have
ClassLoaderproblems [1]. According their JIRA task [2], Hibernate is moving away from Commons-Logging to SLF4J because of that. Jetty also moved from Commons-Logging (Jetty 5) to SLF4J (Jetty 6) [3], which is causing the trouble that Andrea reported to us and trigged this logging discussion.[1] http://www.qos.ch/logging/classloader.jsp
[2] http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696
[3] http://groups.google.com/group/buildr-talk/browse_thread/thread/bbaadd048af6ffad
However, we could said "use SLF4J" instead and this comment would not be applicable anymore. So I suggest to interpret this proposal as "Use SLF4J" (http://www.slf4j.org/).