You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Apache Wiki <wi...@apache.org> on 2006/01/19 22:24:47 UTC
[Jakarta-commons Wiki] Update of "Logging/1.1.0ReleasePlan" by DennisLundberg
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.
The following page has been changed by DennisLundberg:
http://wiki.apache.org/jakarta-commons/Logging/1%2e1%2e0ReleasePlan
------------------------------------------------------------------------------
== Bug Review ==
- * Bug 31286 ''[logging] Memory leaks in JBoss due to Log``Factory cache''
- * Bug 32618 ''[logging] Enterprise Commons Logging : Globalization & more''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=31286 31286] ''[logging] Memory leaks in JBoss due to Log``Factory cache'' '''FIXED'''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=32618 32618] ''[logging] Enterprise Commons Logging : Globalization & more''
* IBM's (through Richard) proposal which seems too much for this release.
- * Bug 35774 ''[logging] TCCL problem in J2EE Container''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=35774 35774] ''[logging] TCCL problem in J2EE Container''
- * Bug 36041 ''[logging] Include class loader information when Log``Factory``Impl throws Log``Configuration``Exception.''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=36041 36041] ''[logging] Include class loader information when Log``Factory``Impl throws Log``Configuration``Exception.'' '''FIXED'''
* Reporter has been asked if it's OK to close this issue.
- * Bug 36062 ''[logging] extended API: getChildLogger(String)''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=36062 36062] ''[logging] extended API: getChildLogger(String)''
* The two Joergs have said on the dev-list that they are willing to wait until a later release with this one.
- * Bug 36927 ''[logging] Disabling of TCCL''
- * Bug 37067 ''[logging] enhancement : add support for ant task logger''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=36927 36927] ''[logging] Disabling of TCCL'' '''Implemented, needs testing'''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=37067 37067] ''[logging] enhancement : add support for ant task logger''
* Waiting for someone to create a patch.
- * Bug 37420 ''[logging] Online JCL 1.0.4 API Javadoc missing''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=37420 37420] ''[logging] Online JCL 1.0.4 API Javadoc missing''
- * This is a website issue. Someone needs to change a link. The process of copying the api-docs for a previous release should be documented, if it isn't already.
+ * This is a website issue. Someone needs to change a link. The process of copying the api-docs for a previous release should be documented, if it isn't already. '''FIXED'''
- * Bug 37427 ''[logging] Redirect stdout and stderr to logging system''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=37427 37427] ''[logging] Redirect stdout and stderr to logging system''
- * Simon and Robert agrees that this should not go into commons logging.
+ * Simon and Robert agrees that this should not go into commons logging. '''WONTFIX'''
- * Bug 37484 ''[logging] call to getClassLoader() in Log``Factory``Impl not checked for null''
+ * Bug [http://issues.apache.org/bugzilla/show_bug.cgi?id=37484 37484] ''[logging] call to getClassLoader() in Log``Factory``Impl not checked for null''
* Might have been solved already.
== Bug Fixes ==
@@ -46, +46 @@
* Sort out whether we split Log4JLogger into two classes or not. If we choose two classes, how should we name them?
1. Rename Log4``J12``Logger.java back to Log4JLogger.java. That would make the upgrade transparent for the previous use-case. But there is the chance that this will not work at all for a user that is currently using JCL 1.0.4 together with log4jalpha-something and a configuration file stating that Log4JLogger should be used.
1. Users who configure JCL to use Log4JLogger might reasonably expect JCL to guess the log4j version and use the correct logger. so, perhaps one option would be to create a delegating implementation.
-
+ 1. Same as #1 but kick out Log4``J13``Logger, because Log4``J 1.3 has not been released.
* Decide our jar distribution strategy (in particular, whether we ship the optional jar or not).
* How do we give downstream packagers and users a fair view of the actual JCL dependencies?
@@ -56, +56 @@
* eliminate optional jar '''DONE'''
''sub-components don't work very well. in particular, i think too
- many users are going to get too confused by yet another jar. WeakHashMap
+ many users are going to get too confused by yet another jar. Weak``Hash``Map
will go into the base distribution, other classes will be moved into
contrib. perhaps another component (logging-extras) would be good or
perhaps moving them off shore.''
@@ -75, +75 @@
''log4j 1.3 is still not released. the new JCL release cannot depend on
unreleased code. the 1.3 implementation will be moved into contrib.
- Log4JLogger and Log4J12Logger will be shipped with notes that direct use
+ Log4JLogger and Log4``J12``Logger will be shipped with notes that direct use
of log4jlogger is deprecated and will be replaced by a logical logger
when log4j 1.3 ships.''
- * ServletContextCleaner ''this will be shipped''
+ * Servlet``Context``Cleaner ''this will be shipped''
* IoC friendly design ''postponed''
== Test Compatibility ==
- Verify that TRACE support works for Log4J 1.2.12+. ''DONE''
+ Verify that TRACE support works for Log4J 1.2.12+. '''DONE'''
== Release Notes ==
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org