You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2006/03/14 08:04:43 UTC
DO NOT REPLY [Bug 38959] New: - [configuration] Drop 1st class dependency on commons-logging
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
Summary: [configuration] Drop 1st class dependency on commons-
logging
Product: Commons
Version: 1.2 Final
Platform: Other
OS/Version: All
Status: NEW
Severity: minor
Priority: P3
Component: Configuration
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: joerg.schaible@gmx.de
Currently commons-logging is reported as first class dependency in the project
reports. This is not true. The only classes that make direct usage of JCL are
ConfigurationDynaBean/Class and this only for tracing. It would be nice to
eliminate this reference at all and list JCL only as transitive dependency of
digester and beanutils.
We might support logging with the monitor/listener concept of
http://issues.apache.org/bugzilla/show_bug.cgi?id=38929
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From ebourg@apache.org 2006-03-16 13:29 -------
I'm not fond of using monitors instead of Commons Logging, I'd prefer to keep
the dependency. No one really complained about it, it's such a common dependency
nowadays.
In the event of upgrading the JDK requirement from 1.3 to 1.4, I would be +1 for
replacing JCL by java.util.logging. In the meantime maybe we could provide a
separate jar (commons-configuration-1.x-nolog.jar) produces through byte code
engineering to remove the logging statements?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From joerg.schaible@gmx.de 2006-03-16 15:09 -------
The problem arises, if you use a Configuration to select the log system to used
by commons-logging by setting the appropriate system property. And if you have
multiple environments it does not help to use a *single*
commons-logging.properties file. Currently I have to call
LogFactory.releaseAll() to get rid of any already already allocated JCL loggers
and additionally LogManager.getLogManager().readConfiguration() in case the JDK
logger is used.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From joerg.schaible@gmx.de 2006-03-15 08:31 -------
Ups. You're right. Eclipse (3.2M5) fooled me, it only marks one class as
erroneous if I drop the dependency (must be new behavior). Nevertheless the
monitor approach from 38929 could be used to implement a logging listener, e.g.
look at ConfigurationUtils: All debug outputs are related to a reload operation
of a configuration.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From bayard@apache.org 2006-03-15 07:41 -------
Seems to be used in more than just those two classes.
./src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaBean.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaBean.java:import
org.apache.commons.logging.LogFactory;
./src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java:import
org.apache.commons.logging.LogFactory;
./src/java/org/apache/commons/configuration/ConfigurationFactory.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/ConfigurationFactory.java:import
org.apache.commons.logging.LogFactory;
./src/java/org/apache/commons/configuration/ConfigurationUtils.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/ConfigurationUtils.java:import
org.apache.commons.logging.LogFactory;
./src/java/org/apache/commons/configuration/DatabaseConfiguration.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/DatabaseConfiguration.java:import
org.apache.commons.logging.LogFactory;
./src/java/org/apache/commons/configuration/JNDIConfiguration.java:import
org.apache.commons.logging.Log;
./src/java/org/apache/commons/configuration/JNDIConfiguration.java:import
org.apache.commons.logging.LogFactory;
./src/test/org/apache/commons/configuration/test/HsqlDB.java:import
org.apache.commons.logging.Log;
./src/test/org/apache/commons/configuration/test/HsqlDB.java:import
org.apache.commons.logging.LogFactory;
./src/test-cactus/org/apache/commons/configuration/TestConfigurationFactoryWithJNDI.java:import
org.apache.commons.logging.Log;
./src/test-cactus/org/apache/commons/configuration/TestConfigurationFactoryWithJNDI.java:import
org.apache.commons.logging.LogFactory;
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From thorbjoern@gmail.com 2007-06-01 05:27 -------
I am in the process of migrating our Java code to use slf4j and I found that the
AbstractConfiguration class makes an explicit reference to the
org.apache.commons.logging.impl.NoOpLog which is an internal class to commons
logging in my mind (the impl package).
It - naturally - causes a runtime failure.
I am not certain if this is enough to warrant a completely new bug, but it
definitively underlines that this is a hard dependency.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From oliver.heger@t-online.de 2006-03-15 19:34 -------
We don't log really useful or exciting things, so I am +1 for removing the
references to commons-logging. The only interesting information is probably
where configuration files are searched and why they cannot be loaded when an
error occurs. If this can be provided through an event listener or through
better diagnostic messages of the thrown exceptions, then be it!
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From dennisl@apache.org 2007-06-01 05:41 -------
Please make any comments you have on this issue in JIRA
https://issues.apache.org/jira/browse/CONFIGURATION-3
We have switched issue tracking systems.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 38959] - [configuration] Drop 1st class dependency on commons-logging
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38959>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38959
------- Additional Comments From ebourg@apache.org 2006-03-16 15:41 -------
I see your point. Maybe it would be wiser to use the good old
java.util.Properties instead of a Configuration to load the logging settings ?
Alternatively we could add a setLog(Log) method to the configurations like
[digester]. This may solve your issue since LogFactory.getLog() will no longer
be called, but that'll keep the dependency on JCL.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org