[jboss-jira] [JBoss JIRA] Updated: (JBSER-100) Please do not require log4j
[ http://jira.jboss.com/jira/browse/JBSER-100?page=all ]
David Lloyd updated JBSER-100:
------------------------------
Summary: Please do not require log4j (was: Please change to JDK logging)
Fix Version/s: 1.1.0 Beta
Description: Using log4j is not acceptable to projects that don't use log4j (for
example, Remoting 3). Using jboss-common-logging would be acceptable, as would using JDK
logging. (was: Frameworks that require logging should always use JDK logging. Otherwise,
a dependency is imposed on all user code that makes use of the framework.
Please change JBoss Serialization to use JDK logging.)
Complexity: Low
Switching to jboss common logging would be fine as well, so I'm updating this issue
accordingly.
Please do not require log4j
---------------------------
Key: JBSER-100
URL: http://jira.jboss.com/jira/browse/JBSER-100
Project: JBoss Serialization
Issue Type: Feature Request
Reporter: David Lloyd
Assigned To: Clebert Suconic
Fix For: 1.1.0 Beta
Using log4j is not acceptable to projects that don't use log4j (for example, Remoting
3). Using jboss-common-logging would be acceptable, as would using JDK logging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira