RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Ceki Gülcü
At 11:53 PM 10/29/2004, Scott Deboy wrote: Are there other changes to HEAD that should have been deprecation warnings in 1.2.8 other than Category? The only thing I can recall off the top of my head is LocationInfo. Generally speaking, your point is really an excellent one. As Brian W. Kernighan

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Ceki Gülcü
At 11:53 PM 10/29/2004, Scott Deboy wrote: Are there other changes to HEAD that should have been deprecation warnings in 1.2.8 other than Category? The only thing I can recall off the top of my head is LocationInfo. Generally speaking, your point is really an excellent one. As Brian W. Kernigha

Re: [POLL] a 1.2.9 release?

2004-11-01 Thread Ceki Gülcü
At 02:12 AM 11/1/2004, Raymond DeCampo wrote: Ceki, What about the Priority class? Aren't there similar problems there? Good point. Let me check and get back to you. Also, will anything else be in the 1.2.9 version (relative to 1.2.8)? No. All new features go into 1.3. Thanks, Ray -- Ceki Gülcü

Re: MultiplexAppender & Joran

2004-11-01 Thread Ceki Gülcü
Hi Paul, Sorry it took so long to respond. Given the 1.2.9 situation I don't have the time to look into MultiplexAppender. However, I'll do so after 1.2.9 is released. Nevertheless, from a cursory look I can say that given the number of appenders in log4j, it looks unrealistic to have as many appen

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Shapira, Yoav
Hi, +1 to 1.2.9 with: - Deprecated Category - Deprecated Priority - enum keyword replacement to allow J2SE 5.0 compilation I understand and still +1 if only the first two can be done, but the 3rd one is good as well. -1 on adding other new things, such as some of the recently proposed appender

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Scott Deboy
My point wasn't to try and ensure backward compatibility - it was that we should follow a consistent deprecation policy everywhere. If the class is public and not marked as deprecated, we should mark them deprecated. http://java.sun.com/j2se/1.4.2/docs/guide/misc/deprecation/deprecation.html A

cvs commit: logging-log4j/src/java/org/apache/log4j/varia/test Loop.java

2004-11-01 Thread ceki
ceki2004/11/01 08:11:58 Modified:src/java/org/apache/log4j Tag: v1_2-branch LogManager.java src/java/org/apache/log4j/chainsaw Tag: v1_2-branch ControlPanel.java DetailPanel.java ExitAction.java LoadXMLAction.java Main.ja

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/helpers BoundedFIFOTestCase.java CyclicBufferTestCase.java

2004-11-01 Thread ceki
ceki2004/11/01 08:31:11 Modified:examples Tag: v1_2-branch MyPatternLayout.java NumberCruncherServer.java SortAlgo.java Trivial.java src/java/org/apache/log4j/jmx Tag: v1_2-branch Agent.java src/java/org/ap

cvs commit: logging-log4j/src/java/org/apache/log4j/spi RootLogger.java

2004-11-01 Thread ceki
ceki2004/11/01 08:45:50 Modified:src/java/org/apache/log4j Tag: v1_2-branch Priority.java Added: src/java/org/apache/log4j/spi Tag: v1_2-branch RootLogger.java Log: Adding RootLogger which replaces RootCategory Revision ChangesPath No

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Ceki Gülcü
At 03:23 PM 11/1/2004, Scott Deboy wrote: As an aside, in my opinion there is no reason LocationInfo couldn't have stayed in spi and the location info extractors lived in spi.location. I understand. My point is that LocationInfo is not public because it belongs to the o.a.l.spi package. -- Ceki

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/helpers BoundedFIFOTestCase.java CyclicBufferTestCase.java

2004-11-01 Thread ceki
ceki2004/11/01 09:08:03 Modified:examples/subclass Tag: v1_2-branch MyLogger.java MyLoggerTest.java src/java/org/apache/log4j Tag: v1_2-branch Priority.java src/java/org/apache/log4j/xml/test Tag: v1_2-branch

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Jacob Kjome
+1 if ditto what Yoav said. Jake Quoting "Shapira, Yoav" <[EMAIL PROTECTED]>: > > Hi, > +1 to 1.2.9 with: > - Deprecated Category > - Deprecated Priority > - enum keyword replacement to allow J2SE 5.0 compilation > > I understand and still +1 if only the first two can be done, but the 3rd one >

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Mark Womack
+1 What is the current plan for the 1.3 release? -Mark -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 9:35 AM To: Log4J Developers List Subject: RE: [POLL] a 1.2.9 release? +1 if ditto what Yoav said. Jake Quoting "Shapira, Yoav" <[EMAI

RE: [POLL] a 1.2.9 release?

2004-11-01 Thread Ceki Gülcü
Yoav, Since everyone seems to agree with you, let me just clarify one point. When you say "deprecated Category", you probably mean "deprecate the Category.getRoot and Category.getInstance methods" because given that Logger extends Category, it is impossible to mark the entire Category class as dep

cvs commit: logging-log4j/docs/images ceki-72x101.gif chainsaw-fullscreen-small.jpg chainsaw-fullscreen.jpg coverSmall.png mark-72x99.gif psmith.jpg yshapira.bmp

2004-11-01 Thread ceki
ceki2004/11/01 11:34:29 Added: docs/images Tag: v1_2-branch ceki-72x101.gif chainsaw-fullscreen-small.jpg chainsaw-fullscreen.jpg coverSmall.png mark-72x99.gif psmith.jpg yshapira.bmp Log: added missing ima

cvs commit: logging-log4j/src/xdocs documentation.xml download.xml

2004-11-01 Thread ceki
ceki2004/11/01 12:41:22 Modified:src/xdocs documentation.xml download.xml Log: preparing for 1.2.9 Revision ChangesPath 1.43 +3 -3 logging-log4j/src/xdocs/documentation.xml Index: documentation.xml =

cvs commit: logging-log4j/docs HISTORY download.html documentation.html

2004-11-01 Thread ceki
ceki2004/11/01 12:45:50 Modified:docs HISTORY download.html documentation.html Log: Chages reflecting the release of 1.2.9 Revision ChangesPath 1.117 +16 -0 logging-log4j/docs/HISTORY Index: HISTORY ==

Release of log4j version 1.2.9

2004-11-01 Thread Ceki Gülcü
Hello all, The log4j developers are pleased to announce the release of log4j version 1.2.9. Log4j version 1.2.9 is identical to version 1.2.8, except that several key methods have been deprecated in preparation for version 1.3.0, the next major release of log4j. These changes are intended to enforc