Venu,
This is the first paragraph of the plan:
"Here is my proposed plan for the next major log4j release. As customary, there is no
scheduled release date. It will be ready when it is ready. Your comments and
suggestions are most welcome."
Regards, Ceki
ps: See http://jakarta.apache.org/lo
hi,
i found the released plan for log4j 1.2.
i need to know when the 1.2 is going to release... it could be
better to know the date correctly...
thanks in advance.
cheers,
Venu
-
Umair,
I recently modified PropertyConfigurator to allow the configuration of
category factories. I agree that the same should be done for
DOMConfigurator. I just haven't gotten around to it. If you have a
suggestion for the necessary modifications, I'd be glad to take a look at
it.
- Paul
P
I am working with Log4J and have extended the Category
class and to be able to use the DOMConfigurator class
I need to set the correct CategoryFactory.
Its current behaviour is to use the default category factory
from the Hierarchy. PropertyConfigurator on the other hand
has the ability to setup
ceki01/06/19 11:45:27
Modified:buildbuild.xml
docs HISTORY critique.html
src/java/org/apache/log4j/spi ThrowableInformation.java
Log:
The last commit before tagging the jakarta-log4j module.
Revision ChangesPath
1.37 +6 -0
Greetings,
This release corrects a bug in log4j.dtd that prevented it from
working in the recent namespace aware XML parsers. This version
introduces no new code.
HISTORY file reads:
- Release of version 1.1.3
- Added a missing namespace declaration in the log4j:configuration
element
ceki01/06/19 08:45:09
Modified:docs HISTORY critique.html download.html
src/java/org/apache/log4j BasicConfigurator.java
Category.java Hierarchy.java
src/java/org/apache/log4j/performance NotLogging.java
src/ja
Paul,
All you need to do is add the "@deprecated" to the method or class javadoc. It
is also recommend to include a "@see" tag to reference the method or class that
should be now called or replaced with.
--Claudio
> From: "Paul Glezen" <[EMAIL PROTECTED]>
> Date: Tue, 19 Jun 2001 07:18:01 -070
Yes, use @deprecated :
/**
@deprecated As of version x.y, replaced by {@link #newMethod()}
*/
- Original Message -
From: "Paul Glezen" <[EMAIL PROTECTED]>
To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 19, 2001 7:18 AM
Subject: Method Deprecation
> How d
Good point, Endre.
It's just that the issue came up for me while working on log4j.
Thanks for the overwhelming responses.
- Paul
Paul Glezen
IT Specialist
Software Services
818 539 3321
Endre Stølsvik <[EMAIL PROTECTED]> on 06/19/2001 07:28:23 AM
Please respond to "LOG4J Developers Mailing
On Tue, 19 Jun 2001, Paul Glezen wrote:
| How does one mark a method as deprecated? Will doing so in the Javadoc
| comments accomplish this?
Yes, but is this log4j related at all?
--
Mvh,
Endre
-
To unsubscribe, e-mail: [E
Title: RE: Method Deprecation
just add @deprecated in the /** */ comment
>-Original Message-
>From: Paul Glezen [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, June 19, 2001 4:18 PM
>To: LOG4J Developers Mailing List
>Subject: Method Deprecation
>
>
>How does one mark a method as deprecat
How does one mark a method as deprecated? Will doing so in the Javadoc
comments accomplish this?
Thanks,
- Paul
Paul Glezen
IT Specialist
Software Services
818 539 3321
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
ceki01/06/19 00:24:37
Modified:docs critique.html
Added: docs plan.html
Log:
100 and counting.
Revision ChangesPath
1.10 +110 -87 jakarta-log4j/docs/critique.html
Index: critique.html
=
14 matches
Mail list logo
