On May 30, 2008, at 11:59 AM, Shriver, Daniel wrote:
I've finally found that the LogFilePatternReceiver is in a separate
bundle ("receivers") that oddly has the same package structure as
log4j. Unfortunately when I try to build it maven spits out an error
saying:
Missing:
--
1) log
I've finally found that the LogFilePatternReceiver is in a separate
bundle ("receivers") that oddly has the same package structure as
log4j. Unfortunately when I try to build it maven spits out an error
saying:
Missing:
--
1) log4j:apache-log4j-component:jar:1.0-SNAPSHOT
1) where d
On Thu, Sep 07, 2006 at 10:12:39PM -0700, Scott Deboy wrote:
> Do you have control over the file format?
I do...
> Can you hard-code spaces to the left and right of the (possibly non-existent)
> NDC? For example:
...and I can, so I will. It does solve the problem, so thank you.
> DEBUG: [200
Interesting...
Do you have control over the file format?
Can you hard-code spaces to the left and right of the (possibly non-existent)
NDC? For example:
DEBUG: [2006-09-07 13:48:03,155] package.foo( ) - message foo
DEBUG: [2006-09-07 13:48:03,187] package.bar( ) - message bar
DEBUG: [2006-09-
I can't imagine ls having an effect on Chainsaw/LogFilePatternReceiver.
This could be a 'refresh' problem in Chainsaw - try this:
Do whatever you need to do to cause 'ls' to do its trick.
Instead of using ls, just minimize Chainsaw and restore it.
Do the events display correctly?
If so, you m
LogFilePatternReceiver relies on the ORO library - add it to your
classpath and everything should work fine.
Scott
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rakesh Patel
Sent: Monday, August 29, 2005 12:14 PM
To: [email protected]
Subject: LogFilePat
