+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
Author: psmith
Date: Sun Jun 10 22:29:22 2007
New Revision: 546016
URL: http://svn.apache.org/viewvc?view=rev&rev=546016
Log:
Relocating zeroconf tests to companion module.
Added:
logging/log4j/companions/zeroconf/trunk/src/test/java/org/apache/log4j/net/
- copied from r546015,
loggi
Author: psmith
Date: Sun Jun 10 22:28:05 2007
New Revision: 546015
URL: http://svn.apache.org/viewvc?view=rev&rev=546015
Log:
updating src folders for test case move.
Added:
logging/log4j/companions/zeroconf/trunk/src/test/java/org/
logging/log4j/companions/zeroconf/trunk/src/test/java/o
Author: psmith
Date: Sun Jun 10 22:14:36 2007
New Revision: 546010
URL: http://svn.apache.org/viewvc?view=rev&rev=546010
Log:
Removed mvn archetype test.
Removed:
logging/log4j/companions/zeroconf/trunk/src/test/java/log4j/AppTest.java
--
Author: psmith
Date: Sun Jun 10 22:12:56 2007
New Revision: 546009
URL: http://svn.apache.org/viewvc?view=rev&rev=546009
Log:
Relocating the zeroconf to a seperate companion module.
Added:
logging/log4j/companions/zeroconf/trunk/src/main/java/org/apache/log4j/net/
- copied from r546008
Author: psmith
Date: Sun Jun 10 22:09:57 2007
New Revision: 546008
URL: http://svn.apache.org/viewvc?view=rev&rev=546008
Log:
Adding basic project structure for the log4j-zeroconf companion module.
Added:
logging/log4j/companions/zeroconf/
logging/log4j/companions/zeroconf/trunk/
lo
I'd probably make a new companion module for it, but you could just add the
classes to receivers, since it already contains both appenders and receivers.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax
I moved the Zeroconf source directory recently into the main Chainsaw
source tree, which I think is a mistake.
Chainsaw needs to have it, but a standalone jar is needed in the
client end to zeroconf-enable the application to expose it on the
network.
It make more sense to create a log4j-z
One other thing: if we don't plumb repository properties to loggingevent MDC,
we should remove the properties code in logger RepositoryEx
I do think an argument could be made in support of keeping repository-wide
properties (determining source of an event once the events have been combined
(db,
I think I've done everything I'll need in the short term, so feel
free to consolidate stuff into a parent pom.
On 09/06/2007, at 5:57 PM, Curt Arnold wrote:
I'm probably not going to get to it in the next day or so, but I've
been thinking about looking at the Chainsaw POM and seeing what if
The goal was to get events generated by LogUI's logger calls to route to its
own tab called "chainsaw-log".
Ideally, other events which were handed over to Chainsaw via a receiver, but
which didn't have the hostname & application properties defined would end up on
a separate tab ("-" instead
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax:503.222.0185
[EMAIL PROTECTED]
www.comotivsystems.com
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Sun 6/
Author: carnold
Date: Sun Jun 10 13:02:11 2007
New Revision: 545927
URL: http://svn.apache.org/viewvc?view=rev&rev=545927
Log:
Bug 42094: Add PluginConfigurator to log4j 1.3 for compatibility with log4j 1.2
+ component companion
Added:
logging/log4j/trunk/src/java/org/apache/log4j/plugins/P
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-chainsaw has an issue affecting its community integration.
This iss
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-chainsaw has an issue affecting its community integration.
This iss
On Jun 10, 2007, at 2:57 AM, Scott Deboy wrote:
log4j 1.3 included the ability to set properties at the logger
repository level (if it was a loggerrepositoryex) - logger
repository properties would be added to all events associated with
the repository.
That feature isn't currently availa
On Jun 10, 2007, at 3:28 AM, Scott Deboy wrote:
If I recall, we added support in 1.3 PatternLayout for more-than-
one character pattern names (like %properties).
We use this feature in Chainsaw to display ALL of the properties on
the event.
I'm not sure how much work it is to bring that i
If I recall, we added support in 1.3 PatternLayout for more-than-one character
pattern names (like %properties).
We use this feature in Chainsaw to display ALL of the properties on the event.
I'm not sure how much work it is to bring that in or if it's worth it, but I do
need this feature (we
log4j 1.3 included the ability to set properties at the logger repository level
(if it was a loggerrepositoryex) - logger repository properties would be added
to all events associated with the repository.
That feature isn't currently available in the 1.2.15 codebase, and I was
curious if it's
19 matches
Mail list logo
