chainsaw commit msg

FYI: chainsaw commit msgs not yet working - here's the info: sdeboy 2005/02/24 23:26:01 Modified:src/java/org/apache/log4j/chainsaw/receivers known.receivers .build.xml Added: src/java/org/apache/log4j/chainsaw/vfs VFSLogFilePatt

Gump all clear

The Cactus builds still fail in the same manner when run with log4j 1.2, so I assume that their breakage was just coincidental with our breaking hivemind. With my recent changes, there is no need to change Hivemind. It does not appear that the internal logging suppression was totally effe

Pattern specifiers for abbreviated logger and class names

I wanted to get opinions on adding support in the pattern layout for abbreviated forms of the logger and class names. Fully qualified class names and logger names typically are fairly long and could be usually be radically abbreviated with little loss of information. For example, a logger na

Re: Gump for Chainsaw

On Feb 24, 2005, at 10:28 PM, Paul Smith wrote: we probably should be consistent. I wouldn't even know where to start on doing this. Would you be able to help and then show us the process? Cut and paste, my friend, cut and paste. I've committed adding an entry for logging-chainsaw.xml to gum

Re: Gump for Chainsaw

we probably should be consistent. I wouldn't even know where to start on doing this. Would you be able to help and then show us the process? thanks Curt, Paul Curt Arnold wrote: If you don't know, all Apache committers have commit rights to the gump repository so they can keep there project de

Gump for Chainsaw

If you don't know, all Apache committers have commit rights to the gump repository so they can keep there project descriptions current. I don't know if you had plans to get Gump starting to build against Chainsaw's new home. If you'd like me to take a stab at it, let me know. Too late for to

[Fwd: failure notice]

Bummer, the commit notices are failing, here's what I just committed. Paul --- Begin Message --- Hi. This is the qmail-send program at apache.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAI

[Fwd: failure notice]

Ahhh, I thought I'd forget something.   Hi infrastructure, is it possible for us to please have '[EMAIL PROTECTED]' configured to go to the log4j-dev list? cheers, Paul Original Message Subject: failure notice Date: 25 Feb 2005 0

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/filter FilterModel.java EventTypeEntryContainer.java

psmith 2005/02/24 19:17:34 Removed: src/java/org/apache/log4j/chainsaw/icons ZoomIn16.gif Open24.gif Home16.gif TipOfTheDay24.gif New24.gif Zoom16.gif Delete16.gif Forward24.gif RowInsertAfter16.gif Play24.gif Home2

cvs commit: logging-log4j build.xml

psmith 2005/02/24 19:11:30 Modified:.build.xml Log: First part of moving out Chainsaw into it's own module. This tidys up the log4j build process to not need to reference chainsaw at all. Note: I've explicity added the ListModelAppender into the log4j core via this chang

AppenderSkeleton.isActive, etc

I've committed some tweaks that I think should leave us in pretty good condition. I've modified the Gump descriptor for Cactus so that it should attempt to build against log4j 1.2 tonight which should allow us to tell if the recent breakage was due our recent changes. I've restored the test of

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/performance NullAppender.java

carnold 2005/02/24 14:56:21 Modified:contribs/Jamie JMSQueueAppender.java contribs/JayFunnell NetSendAppender.java src/java/org/apache/log4j AppenderSkeleton.java AsyncAppender.java WriterAppender.java src/java/org/apac

Re: [VOTE]: Chainsaw as seperate module

As part of the preparations for this move I have tagged the HEAD of logging-log4j as so: cvs rtag TAG_CHAINSAW2_MOVE logging-log4j cheers, Paul Paul Smith wrote: Thanks Ceki for doing this. I was in the last phase of preparing the module when Ceki reminded me that we can copy the CVS history ove

Re: [VOTE]: Chainsaw as seperate module

Thanks Ceki for doing this. I was in the last phase of preparing the module when Ceki reminded me that we can copy the CVS history over if we do some funky CVS tricks. My local repository had just copied the files. We would have had the history in the logging-log4j module, but not in logging-c

Re: log4j release?

On Thu, 2005-02-24 at 10:41, Ceki GÃlcà wrote: > Hi Mark, > > I'd like to see log4j released for around June of this year. As such, log4j > needs to enter into a consolidation and testing phase. There are a number > of issues that need to be resolved. Here is a non-exhaustive list: I'd like to

Re: log4j release?

On Feb 24, 2005, at 12:41 PM, Ceki Gülcü wrote: Hi Mark, I'd like to see log4j released for around June of this year. As such, log4j needs to enter into a consolidation and testing phase. There are a number of issues that need to be resolved. Here is a non-exhaustive list: - Improved documentat

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/joran/spi SimpleRuleStore.java

This makes sense. I assume all actions are processed by SimpleRuleStore.addRule(). -Mark > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 24, 2005 11:26 AM > To: [EMAIL PROTECTED] > Subject: cvs commit: logging-log4j/src/java/org/apache/

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/joran/action Action.java RepositoryPropertyAction.java

Placing objects shared by multiple actions at the bottom of the execution context stack is the usual pattern for managing shared objects in Joran. Since LR happens to be also set through SimpleRuleStore, we get two redundant ways of accessing the LR. Both are correct and existing actions can

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

ceki2005/02/24 11:25:58 Modified:src/java/org/apache/log4j/joran/action Action.java RepositoryPropertyAction.java src/java/org/apache/log4j/joran/spi SimpleRuleStore.java Log: SimpleRuleStore already sets up the LR. Revision Changes

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/joran/action Action.java RepositoryPropertyAction.java

Hey Ceki, I'll have to look at the specific code you are referring to tonight, I don't have the code in front of me. But it sounds like I should replace all the code that accesses the bottom of the stack with code to access whatever SimpleRuleStore sets up. And clean up what I have already added

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/joran/action Action.java RepositoryPropertyAction.java

Hi Mark, What you have done makes perfect sense. However, the addRule method in SimpleRuleStore already sets the LoggerRepository for all Action instances that JoranConfigurator refers to. There is no point in adding a getLoggerRepository in Action if it is already in ComponentBase. In other wo

Re: Reverting Appender interface

Actually, looking at the Gump messages in the Hivemind mailing list suggest that the problem was all along the lack of an activateOptions call before adding an appender and was never the addition of isClosed(), isActive() and activate. Please apply the following patch, this should resolve th

Re: log4j release?

Hi Mark, I'd like to see log4j released for around June of this year. As such, log4j needs to enter into a consolidation and testing phase. There are a number of issues that need to be resolved. Here is a non-exhaustive list: - Improved documentation - More Joran tests - Mote integration tests w

Re: Using log4j Appender classes in java.util.logging

Hello Javier, Thank you for writing to us. The type of bridging effort you describe get quite complicated fairly quickly. In this particular case, that is Handler->Appender type bridging, I fail to see the long term added value to our users. However, I'd like to encourage you to set up a separa

Re: Reverting Appender interface

Hello Knut, We'd like to reintroduce the isClosed(), isActive() and activate() methods back into the Appender interface. Since these methods are already implemented by AppenderSkeleton, existing appenders should remain compile-time compatible. Do you remember if there were any compile time issu

RE: Using log4j Appender classes in java.util.logging

Chainsaw V2 provides some support for processing of java.util.logging-creatd events in two ways: - Chainsaw can load files formatted by java.util.logging's XmlFormatter - Chainsaw can receive events sent by java.util.logging's SocketHandler Scott -Original Message- From: Camara Melgo

Using log4j Appender classes in java.util.logging

Title: Mensaje Hi. I have just created a java.util.logging.Handler class allowing to plug-in regular Appender classes in the java.util.logging system, so that applications using this system can benefit from the large number of Appenders out there. They are plugged in just via standard config

log4j release?

Should we start thinking about some general release timeframe for v1.3? It's been a while since we had a major release, and I think we are getting close with the feature set for v1.3. Is there anything else major that needs to be done for v1.3? - Watchdogs (FileWatchdog, HttpWatchdog, SocketWatch

DO NOT REPLY [Bug 33708] - XML Configuration of loggerFactory does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Gump issues

At 05:47 PM 2/24/2005, Ceki Gülcü wrote: That makes sense because the recent additions are compile-time compatible with existing appenders. The above statement is true for any appender extending AppenderSkeleton because AppenderSkeleton implements the methods newly added to the Appender interfac

Re: Gump issues

Curt, Thanks for following up on this! At 05:24 PM 2/24/2005, Curt Arnold wrote: Commenting out if (!this.active) { getNonFloodingLogger().error( "Attempted to log with inactive appender named [{}].", name); return; } from AppenderSkeleton.doAppend was suffic

cvs commit: logging-log4j/src/java/org/apache/log4j/helpers LogLog.java

ceki2005/02/24 08:32:03 Modified:docs HISTORY.txt src/java/org/apache/log4j/helpers LogLog.java Log: - Chatty output about Logger creation or retrieval events is now suppressed by default. They can be enabled by explicitly setting the log4j.coreD

cvs commit: logging-log4j/src/java/org/apache/log4j/config ConfiguratorBase.java

ceki2005/02/24 08:31:24 Modified:src/java/org/apache/log4j/config ConfiguratorBase.java Log: javadoc changes Revision ChangesPath 1.10 +7 -7 logging-log4j/src/java/org/apache/log4j/config/ConfiguratorBase.java Index: ConfiguratorBase.java ===

Gump issues

Commenting out if (!this.active) { getNonFloodingLogger().error( "Attempted to log with inactive appender named [{}].", name); return; } from AppenderSkeleton.doAppend was sufficient to get hivemind building again. Setting up a Hivemind build was sufficie

Re: [VOTE]: Chainsaw as seperate module

At 06:36 AM 2/24/2005, Paul Smith wrote: ok, only Ceki's vote to go, and I understand he's still recovering from some hardware problems. In a recent mail, Ceki intimated he was, in principle, in favour, so I will _begin_ this process locally, but not commit, and wait until Ceki has a chance to

Re: [VOTE]: Chainsaw as seperate module

+1 OK, then I'll go create the 'logging-chainsaw' CVS module and grant the appropritate karma on the Apache Server. At 10:18 PM 2/23/2005, Paul Smith wrote: This is a formalization of the thread 'Chainsaw as seperate CVS module'. 1. Propose to move out Chainsaw sources into it's own CVS module,

Re: jms text msg appender

Yes, I'm also willing to help maintain a JMSAppender/JMSReceiver pair with the added capability.   Michael Los smime.p7s Description: S/MIME cryptographic signature

Re: [VOTE]: Chainsaw as seperate module

+1 ___ Johan Känngård [EMAIL PROTECTED] http://dev.kanngard.net Paul Smith wrote: This is a formalization of the thread 'Chainsaw as seperate CVS module'. 1. Propose to move out Chainsaw sources into it's own CVS module, 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 bu