You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Geert Schuring (JIRA)" <ji...@apache.org> on 2011/01/03 00:24:46 UTC
[jira] Created: (SMX4-727) Consider dropping commons-logging for
standard Java.util.logging
Consider dropping commons-logging for standard Java.util.logging
----------------------------------------------------------------
Key: SMX4-727
URL: https://issues.apache.org/jira/browse/SMX4-727
Project: ServiceMix 4
Issue Type: Improvement
Affects Versions: 4.2.0
Reporter: Geert Schuring
Fix For: 4.3.0
I would like to see the use of commons-logging API dropped in favor of java.util.logging. I know the implementation of commons-logging/log4j are better but since ServiceMix is Karaf based we always use the Log4j backend, no matter which API we use. And since the java.util.logging API is good enough to be able to distinguish several log levels, I would prefer dropping the dependency on commons-logging.
If the majority of developers disagree on this, then lets comment on this issue with the reasons and we'll close it. At least then we'll have that choice documented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMX4-727) Consider dropping commons-logging for
standard Java.util.logging
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMX4-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMX4-727:
---------------------------------
Fix Version/s: (was: 4.3.0)
4.4.0
Moving this issue to the 4.4.0 release
> Consider dropping commons-logging for standard Java.util.logging
> ----------------------------------------------------------------
>
> Key: SMX4-727
> URL: https://issues.apache.org/jira/browse/SMX4-727
> Project: ServiceMix 4
> Issue Type: Improvement
> Affects Versions: 4.2.0
> Reporter: Geert Schuring
> Fix For: 4.4.0
>
>
> I would like to see the use of commons-logging API dropped in favor of java.util.logging. I know the implementation of commons-logging/log4j are better but since ServiceMix is Karaf based we always use the Log4j backend, no matter which API we use. And since the java.util.logging API is good enough to be able to distinguish several log levels, I would prefer dropping the dependency on commons-logging.
> If the majority of developers disagree on this, then lets comment on this issue with the reasons and we'll close it. At least then we'll have that choice documented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Resolved] (SMX4-727) Consider dropping commons-logging for
standard Java.util.logging
Posted by "Gert Vanthienen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMX4-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SMX4-727.
----------------------------------
Resolution: Won't Fix
As other projects have been moving towards SLF4J (cfr. https://issues.apache.org/jira/browse/AMQ-3177 and https://issues.apache.org/jira/browse/CAMEL-3605), we followed suit and went that way as well for all our code.
> Consider dropping commons-logging for standard Java.util.logging
> ----------------------------------------------------------------
>
> Key: SMX4-727
> URL: https://issues.apache.org/jira/browse/SMX4-727
> Project: ServiceMix 4
> Issue Type: Improvement
> Affects Versions: 4.2.0
> Reporter: Geert Schuring
> Fix For: 4.4.0
>
>
> I would like to see the use of commons-logging API dropped in favor of java.util.logging. I know the implementation of commons-logging/log4j are better but since ServiceMix is Karaf based we always use the Log4j backend, no matter which API we use. And since the java.util.logging API is good enough to be able to distinguish several log levels, I would prefer dropping the dependency on commons-logging.
> If the majority of developers disagree on this, then lets comment on this issue with the reasons and we'll close it. At least then we'll have that choice documented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira