Hi,
+1 for me !
--
Michael CATANZARITI,
Log4cxx Administrator (http://log4cxx.sf.net)
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 7:07 AM
To: [EMAIL PROTECTED]
Subject: [PROPOSAL] Logging services top level project
Hello,
Several
Thanks Paul.
I would be honored to serve as the chairman for Logging Services
project.
Let us wait to see whether my candidacy is endorsed by the other
committers and whether there are other candidates.
At 02:21 PM 12/14/2003 +1100, Paul Smith wrote:
Oh, and as for the potential Chairman, I would
I would welcome any proposal that outlines a concrete integration
path for LogKit.
At 01:15 AM 12/15/2003 +0100, Stephen McConnell wrote:
Ceki :
One item you may want to add is the inclusion of the Avalon LogKit package
in the list of products under the "rationalization" effort. I think this
w
Howdy,
Seems like the natural choice ;) +1.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
>Sent: Monday, December 15, 2003 8:55 AM
>To: [EMAIL PROTECTED]
>Subject: RE: [PROPOSAL] Logging services top level project
>
>
>Thanks Pa
ceki2003/12/15 09:00:55
Modified:src/java/org/apache/log4j/jdbc JDBCReceiver.java
Log:
small doco update
Revision ChangesPath
1.12 +3 -3
jakarta-log4j-sandbox/src/java/org/apache/log4j/jdbc/JDBCReceiver.java
Index: JDBCReceiver.java
==
+1
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 7:49 AM
To: Log4J Developers List
Subject: RE: [PROPOSAL] Logging services top level project
Howdy,
Seems like the natural choice ;) +1.
Yoav Shapira
Millennium ChemInformatics
>---
Thanks Scott. The only active committer we are missing is Jacob. (Mark
is away this week.) I'll take the liberty to update the wiki page of
the proposal.
At 09:44 AM 12/15/2003 -0800, Scott Deboy wrote:
+1
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Monday, Decem
Michael,
Thank you for your vote of confidence. Could you be kind enough to give
your opinion on the C++ ports of log4j, including log4cxx? Why are there 3
of them?
Thanks in advance,
At 01:53 PM 12/15/2003 +0100, Michael CATANZARITI wrote:
Hi,
+1 for me !
--
Michael CATANZARITI,
Log4cxx Ad
+1 for Ceki to be chairman.
Jake
Quoting Ceki Gülcü <[EMAIL PROTECTED]>:
>
> Thanks Scott. The only active committer we are missing is Jacob. (Mark
> is away this week.) I'll take the liberty to update the wiki page of
> the proposal.
>
> At 09:44 AM 12/15/2003 -0800, Scott Deboy wrote:
> >+1
Subject to any new last minute developments, I'll submit the proposal this
Friday.
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-
Hi,
I'm the developer and maintainer of a log4j sister project: Log4PHP.
After reading the initial draft and ml comments I give my "+1" to the LS
project.
Since log4php is a pure port of log4j it's not a problem for me to change the
license.
However, I have some questions:
1. The draft talks abo
At 04:31 PM 12/12/2003 +0100, you wrote:
It's great to hear that ApacheCon was such a success.
Given that it's soon a month since it took place,
IMHO it would be the right time now to publish the slides,
and - maybe even more important - the source code for
the logging domain proposal (or is it al
Hi Marco,
At 08:15 PM 12/15/2003 +0100, you wrote:
Hi,
I'm the developer and maintainer of a log4j sister project: Log4PHP.
After reading the initial draft and ml comments I give my "+1" to the LS
project.
Since log4php is a pure port of log4j it's not a problem for me to change the
license.
Very
Hi all,
+1 on behalf of log4net.
Interoperability with log4j is something we have been working towards for
some time now. We have it for some protocols, but not for others. A single
apache PMC seems the best way to achieve this.
Log4net is already Apache licensed so that is not an issue.
Also +
If no-one has any objections, I am going to place a link within the left
hand page to a Chainsaw page (the chainsaw.xml page within the cvs).
I will also update the entry within the download page to display some
new information and a link to the above page.
regards,
Paul Smith
--
No objections but is the chainsaw page ready?
At 07:49 AM 12/16/2003 +1100, you wrote:
If no-one has any objections, I am going to place a link within the left
hand page to a Chainsaw page (the chainsaw.xml page within the cvs).
I will also update the entry within the download page to display so
On Tue, 2003-12-16 at 08:04, Ceki GÃlcà wrote:
> No objections but is the chainsaw page ready?
Just updating it now. I will be checking in shortly for everyone to
review.
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
ceki2003/12/15 13:40:35
jakarta-log4j/examples/src - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:40:35
jakarta-log4j/examples/src/customLevel - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:40:45
jakarta-log4j/examples/src/factor - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:41:07
jakarta-log4j/examples/src/subclass - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:41:19
jakarta-log4j/examples/src/trivial - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:41:30
jakarta-log4j/examples/src/pattern - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:41:41
jakarta-log4j/examples/src/objectBased - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:41:51
jakarta-log4j/examples/src/jmx - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2003/12/15 13:49:02
Added: examples/src/factor factor.lcf NumberCruncher.java
NumberCruncherServer.java factor.html
NumberCruncherClient.java
examples/src/subclass MyLogger.java MyLoggerFactory.java
ceki2003/12/15 13:57:07
Added: examples/sort sort4.properties Sort.java sort1.properties
sort3.properties sort2.properties SortAlgo.java
Log:
Files moved from examples/ to examples/src/
Revision ChangesPath
1.3 +1 -0 jakarta-log
psmith 2003/12/15 13:59:31
Modified:src/xdocs/stylesheets project.xml
src/xdocs download.xml chainsaw.xml
Added: src/xdocs install-chainsaw.xml
Log:
Added more details to the website about Chainsaw v2.
Added the temporary install-chainsaw.xml script with
This summer, my company asked me to look for a logging framework in
order to ingrate it into our product.
I needed a logging framework in C++, so I took a look at log4cpp and
log4cplus.
Log4cpp is licensed under the LGPL, which was not suitable for my company.
Logcplus is licensed under the APL,
> So I decided to create another port licensed under the APL, and that
> would implement the DOMConfigurator, ODBCAppender, and SMTPAppender.
>
My hat's off to you, that was a good move for the C++ community IMHO.
> About the LS project, I propose that
> - the configuration xml and property fil
We've probably been over this before, but what is the current status of
Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk
on JDK 1.3.1 but chainsaw did not compile.
Thanks,
Ray
-
To unsubscribe, e-mail: [EMA
probably our bad, I need to get a 1.3 JDK installed to help with this.
In the mean time, do you have a compile error output you could shoot to
me?
Having said that, Chainsaw is way better on 1.4.2, while we do want to
maintain at least 1.3 compatability, 1.4.2 is the way to go on the
client side.
psmith 2003/12/15 16:45:26
Modified:src/java/org/apache/log4j/chainsaw LoggerNameTreePanel.java
LogPanelPreferencePanel.java JSortTable.java
FileLoadAction.java ApplicationPreferenceModel.java
ApplicationPreferenceM
On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote:
> We've probably been over this before, but what is the current status of
> Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk
> on JDK 1.3.1 but chainsaw did not compile.
I think I've addressed all the 1.3.1 issues now. Do
sdeboy 2003/12/15 17:00:12
Modified:src/java/org/apache/log4j/chainsaw
ChainsawToolBarAndMenus.java
LoggingEventFieldResolver.java
.build.xml
Log:
Updated lookup for tab placement used by toolbarsandmenus
added
psmith 2003/12/15 17:07:07
Modified:src/java/org/apache/log4j/chainsaw
ChainsawToolBarAndMenus.java LogUI.java
Log:
There is now no need for the ToolbarMenu class to be a
SettingsListener, as this is all handled by the AppPrefModel.
Revision Changes
Currently we have the SettingsManager and associated event objects which
are used to save/load Application wide events. However currently all
the LogPanel settings are saved via standard Serialization. This tends
to be easy to do, but brittle as we add more information to the savable
entity.
I p
Paul Smith wrote:
On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote:
We've probably been over this before, but what is the current status of
Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk
on JDK 1.3.1 but chainsaw did not compile.
I think I've addressed all the 1.3.1 i
Paul Smith wrote:
Currently we have the SettingsManager and associated event objects which
are used to save/load Application wide events. However currently all
the LogPanel settings are saved via standard Serialization. This tends
to be easy to do, but brittle as we add more information to the sa
>
> In general, I think that xml based properties files work better in the
> long run rather than "traditional" *.properties files. The hierarchical
> nature of the xml file is definitely a plus. The drawback is it can be
> more difficult to access and set properties. Perhaps the
> DOMConf
40 matches
Mail list logo
