You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <de...@geronimo.apache.org> on 2006/09/13 10:55:22 UTC
[jira] Created: (GERONIMO-2401) Upgrade commons-logging to 1.1
Upgrade commons-logging to 1.1
------------------------------
Key: GERONIMO-2401
URL: http://issues.apache.org/jira/browse/GERONIMO-2401
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Affects Versions: 1.2
Reporter: Jason Dillon
Assigned To: Jason Dillon
Upgrade commons-logging to the latest release 1.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2401?page=all ]
Jason Dillon updated GERONIMO-2401:
-----------------------------------
Fix Version/s: 2.0
Affects Version/s: 1.2
> Upgrade commons-logging to 1.1
> ------------------------------
>
> Key: GERONIMO-2401
> URL: http://issues.apache.org/jira/browse/GERONIMO-2401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 1.2, 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 2.0
>
>
> Upgrade commons-logging to the latest release 1.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-2401:
-----------------------------------
Fix Version/s: (was: 2.1)
Wish List
Definitely important but will not get into 2.1
> 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: Wish List
>
>
> 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.
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-2401:
-----------------------------------
Fix Version/s: (was: 2.0)
2.1
didn't make it into 2.0
> 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.
[jira] Commented: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2401?page=all ]
Jason Dillon updated GERONIMO-2401:
-----------------------------------
Affects Version/s: 2.0
(was: 1.2)
> Upgrade commons-logging to 1.1
> ------------------------------
>
> Key: GERONIMO-2401
> URL: http://issues.apache.org/jira/browse/GERONIMO-2401
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
>
> Upgrade commons-logging to the latest release 1.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592348#action_12592348 ]
Ceki Gulcu commented on GERONIMO-2401:
--------------------------------------
Perhaps it is too late, but if you are migrating to the SLF4J API, then you might find slf4j-migrator [1] helpful.
HTH,
[1] http://www.slf4j.org/migrator.html
> 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.2
>
>
> 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.
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon updated GERONIMO-2401:
-----------------------------------
Component/s: Logging
dependencies
Fix Version/s: (was: 2.0-M5)
2.0-M7
> 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.0-M7
>
>
> 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.
[jira] Updated: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-2401:
-------------------------------------
Fix Version/s: (was: 2.0-M7)
2.0
> 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.0
>
>
> 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.
[jira] Closed: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon closed GERONIMO-2401.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: Wish List)
2.2
Going with SLF4J as the logging facade instead of the problematic Commons Logging API.
> 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.2
>
>
> 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.
[jira] Commented: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515942 ]
David Jencks commented on GERONIMO-2401:
----------------------------------------
should we consider slf4j instead of commons logging?
> 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.0
>
>
> 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.
[jira] Commented: (GERONIMO-2401) Upgrade commons-logging to 1.1
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592375#action_12592375 ]
Jason Dillon commented on GERONIMO-2401:
----------------------------------------
Ya, too late... the heavy lifting is all done now, not that heavy though ;-)
> 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.2
>
>
> 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.