hoju2005/07/26 21:53:25
Modified:docs HISTORY.txt
Log:
forgot to add compatibility indications
Revision ChangesPath
1.29 +3 -2 logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
===
hoju2005/07/26 21:50:58
Modified:docs HISTORY.txt
Log:
Add some of my recent changes to 1.3 belore I forget
Revision ChangesPath
1.28 +28 -11logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
=
hoju2005/07/26 21:25:25
Modified:docs Tag: v1_2-branch HISTORY.txt
Log:
Update docs/HISTORY.txt for my change
Revision ChangesPath
No revision
No revision
1.27.2.6 +5 -1 logging-log4j/docs/HISTORY.txt
Index: HISTO
On Tue, 2005-07-26 at 09:49 -0700, Mark Palmer wrote:
> My code and needs to be common/lib (i.e. don't want to
> modify the web application war file in any way)
>
> This means log4j needs to be in common/lib as well.
This is more of a user question (and a FAQ really), but here's an idea
I'd lik
carnold 2005/07/26 10:38:14
Modified:docs Tag: v1_2-branch HISTORY.txt
Log:
Update docs/HISTORY.txt for my bugs
Revision ChangesPath
No revision
No revision
1.27.2.5 +30 -0 logging-log4j/docs/HISTORY.txt
Index: HISTORY
I'll do another build of 1.3 alpha when we rc 1.2.12. Any 1.2 changes
should be moved to the main branch before then, to keep them in sync.
I think we should continue with the alpha designation until we have reviewed
the api's and feel that they are "frozen".
And the 1.2.12 stuff should not stop
I have written a open source version of jta for tomcat
that can be used with and the existing version of
apache DBCP. (to be released shortly)
I am using log4j of course:-)
My code and needs to be common/lib (i.e. don't want to
modify the web application war file in any way)
This means log4j nee
I'm going to generate a build for 1.2.12 this evening. Everyone that has
fixed a bug since 1.2.11 should make sure the docs/HISTORY.txt is up to date
with the bug fix info.
-Mark
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 22, 2005 4:07 PM
> To
