ceki01/09/03 15:40:55
Modified:buildbuild.xml
Log:
LogManger is no longer excluded.
Revision ChangesPath
1.42 +0 -1 jakarta-log4j/build/build.xml
Index: build.xml
===
RCS file: /ho
ceki01/09/03 15:39:33
Modified:src/java/org/apache/log4j/spi Makefile
Log:
Revision ChangesPath
1.11 +15 -14jakarta-log4j/src/java/org/apache/log4j/spi/Makefile
Index: Makefile
===
RCS
ceki01/09/03 15:37:30
Added: src/java/org/apache/log4j/varia LevelMatchFilter.java
Log:
In replacement of PriorityMatchFilter.java
Revision ChangesPath
1.1
jakarta-log4j/src/java/org/apache/log4j/varia/LevelMatchFilter.java
Index: LevelMatchF
ceki01/09/03 15:33:21
Added: src/java/org/apache/log4j/spi DefaultRepositorySelector.java
LoggerFactory.java LoggerRepository.java
RepositorySelector.java
Removed: src/java/org/apache/log4j/spi CategoryFactory.java
Log:
Add
ceki01/09/03 15:13:39
Modified:docs HISTORY
Log:
Clarification of the comments.
Revision ChangesPath
1.61 +5 -7 jakarta-log4j/docs/HISTORY
Index: HISTORY
===
RCS file: /home/cvs/ja
ceki01/09/03 15:10:10
Modified:docs HISTORY
src/java/org/apache/log4j Category.java
DefaultCategoryFactory.java Hierarchy.java
Logger.java Makefile PropertyConfigurator.java
src/java/org/apache/log4j/e
Hi Paul,
Have you considered extending SocketAppender to send parameters such as
server name, version, components attribute etc. when connecting to
the SocketServer? In such case, there would be no need to extend the
Category class.
Another solution is to use MDCs to set parameters. They will
Objective
-
Gradually remove the Category class in favor of Logger:
a) starting today, it should be possible to use log4j without ever
seeing a reference to category (be it the class Category or any method
or exception containing the word "category"). An added feature would
be that a ne
This one!! :
| Attempt III --
|
| public class Logger {
|
|
| /**
| @deprecated Category class is deprecated.
| Please use the {link #getLogger} instead
If you are maintaining code for a older pr
