On 09/04/2010, at 1:26 PM, Curt Arnold wrote:
>
> On Apr 7, 2010, at 10:36 PM, Gary Gregory wrote:
>
>> Clearly, since Chainsaw V2 is the current version, it seems odd to deliver
>> the code for Chainsaw V1. This should be deprecated in a point release, 1.3
>> or 2.0, not in a 1.2.x maintenan
Can't yank it from log4j.jar without potentially breaking some app
that actually uses it, but could mark it as deprecated and suggest
checking the jmx companion.
the alternative is to start yanking things out of log4j into a
'legacy' jar. People that wish to upgrade log4j jars, need perh
.surlatable.com).
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time an
If logger implements org.slf4j.Logger, then one can write
String name = "Scott";
logger.debug("Hello Scott");
logger.debug("Hello {}", name);
Both log statements will print as "Hello Scott". However, the latter
log statement will contain 'name' as a parameter. The SLF4J
implementation can choos
On 09/12/2008, at 2:27 AM, saimen54 wrote:
Jacob Kjome wrote:
http://logging.apache.org/log4j/companions/component/index.html
http://logging.apache.org/log4j/companions/extras/index.html
http://logging.apache.org/log4j/companions/receivers/index.html
http://logging.apache.org/log4j/companio
We have found there's a duplicate class in log4j and log4j-extras.
I've upgraded our local environment to a 1.2.16 snapshot with the
extras, and low and behold a Bamboo run failed a test (I got the
chicken.. grrr :) ). We have a test that iterates over the jar's in
the classpath looking f
On 04/09/2008, at 12:33 AM, Jukka Zitting wrote:
Hi,
I found a bunch of classes in org.apache.log4j.servlet under
log4j-sandbox and I'd like to use them to replace our custom Log4J
configuration code in Apache Jackrabbit.
It does sound like a good candidate for log4j-extras which we do plan
I went and finally revisited a patch I proposed about a million years
ago to enable testing of the JMSAppender class using ActiveMQ (Bug
38153).
See my patch below [1]. However when I run the tests locally I'm
getting a compile error:
...
prepare:
[available] DEPRECATED - used to overri
The recent release build environment is a JDK 1.4 javac targeting
JDK 1.1 bytecode. If the Geronimo jars contain JDK 1.5 bytecode,
they won't work with JDK 1.4 compilers. Not sure, but I suspect
that might be the case. Compilers in later JDKs don't support
generating JDK 1.1 bytecode
On 13/08/2008, at 3:16 PM, Curt Arnold wrote:
I'd like to address the following bugs and then get an RC1 for log4j
1.2.16 out
For consideration:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43282 (OSGI
packaging info - seems trivial.. ?)
https://issues.apache.org/bugzilla/show_bug
On 13/08/2008, at 19:27, Thorbjørn Ravn Andersen
<[EMAIL PROTECTED]> wrote:
Curt Arnold skrev den 13-08-2008 07:16:
I've thinking it is likely that we may run into problems with the
geronimo artifacts on earlier JVM's. May have to hack the pom.xml
and rebuild to get compatible byt
The only thing I had to do was to delete the jmx reference in
pom.xml as this is present in the JDK. Then it built and installed
without a hinch (except it took 11 minutes).
That 11 minutes will be all the Maven artifacts being downloaded
(almost nothing to do with log4j - only a handf
I've been on vacation for a week and the backlog of changes to
Bugzilla is daunting. There already was a bug for the log4j 1.2.16
release (bug 43313) and somehow it and the newly introduced one
(Bug 45527) need to be reconciled. I haven't reviewed the new bug
and my opinion of blocking
laptop being repaired, but have dusted off my old trusty PowerBook G4
which still magically works like a charm after 4 years, so I have
mail and web, and can use Eclipse although it's vastly slower than
the intel-based macs under Eclipse (I'd compare the G4 to the MacBook
Pro as a Toyota Pr
I was trying to preserve the external behavior that would occur
with the old code if you did not provide jmxtools.jar at runtime.
As implemented, both the new code and the old code would result in
a NoClassDefFoundError if it was deployed without jmxtools.jar.
However, the likelihood that
I really really really dislike this change.
Errors are not designed for use by programs but by the jvm itself.
I prefer if this change was reverted and the use of a wrapping
runtimeexception instead.
On 06/08/2008, at 5:16, [EMAIL PROTECTED] wrote:
Author: carnold
Date: Tue Aug 5 12:16:
xml as this
is under XP).
Is log4j being built by Gump?
--
Thorbjørn Ravn Andersen "... plus... Tubular Bells!"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTEC
My MBP has died and I'm left with my iPhone until it's repaired.
No dev for me for a few days at least!
Doh!
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm considering adding a dependency to Commons-cli to allow Chainsaw
start script to have some startup options, the driving force being to
allow one to configure a Receiver configuration file to pass to it.
This would mean one could configure an automatic URL via the
preferences as we can
On 04/07/2008, at 9:59 AM, Thorbjørn Ravn Andersen wrote:
Paul Smith skrev den 04-07-2008 00:46:
One of the last tasks to complete before a potential 'release' to
the Webstart version of Chainsaw is building a custom Receiver
artifact output that does not include the J
On 04/07/2008, at 8:54 AM, Scott Deboy wrote:
+1
Not sure about the name chainsaw-receivers (they can be used outside
Chainsaw).
I'm all ears on suggestions! :) I think it blows too, but my brain is
tired this morning.
Paul
---
One of the last tasks to complete before a potential 'release' to the
Webstart version of Chainsaw is building a custom Receiver artifact
output that does not include the JMSReceiver & DBReceiver, both of
which require dependent jars that we obviously can't ship (because we
don't know what
P.S.: The chainsaw shell script is not executable by default on
Linux. I have no knowledge of maven scripts so far, but it might be
just a small change to include this?
The appassembler plugin for Maven does not provide that feature, which
I believe is due to the fact that Java itself can
On 29/06/2008, at 9:55 PM, Oliver Frietsch wrote:
junit.framework.AssertionFailedError: Exception in constructor:
testMRUFileList (java.lang.Error: Unresolved compilation problem:
Ok, I don't get this, it's saying it's a compile error. Can you
please run this inside the Chainsaw project:
The junit error disappeared, yet two tests fail. Output attached in
ZIP file...
Maven stores the detailed failures in a target subfolder. In the
output, it mentions:
C:\Dokumente und Einstellungen\ThinkpadBenutzer\Eigene Dateien\Log4J
Workspace\log4j-chainsaw-maven\target\surefire-repo
Anyway, I'm still not successful. The extras companion does not want
to compile either. I attached the output. Is it possible that the
junit package is missing?! I can't really believe that, as I guess
that it is used by the other packages' tests, too.
This is bizarre. On the command
On 25/06/2008, at 7:30 PM, Oliver Frietsch wrote:
Nothing changed. Total runtime is above one hour.
Paul,
thanks for this hint. I believed that the trunk actually contained the
log4j 2.0 code (where is that?).
I got log4j to compile. However, I had to grab the
NTEventLogAppender
[
https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607389#action_12607389
]
Paul Smith commented on LOG4J2-9:
-
Just to clear up what I actually meant, I wasn't
[
https://issues.apache.org/jira/browse/LOG4J2-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607141#action_12607141
]
Paul Smith commented on LOG4J2-16:
--
I like the terminology 'context' and h
[
https://issues.apache.org/jira/browse/LOG4J2-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607127#action_12607127
]
Paul Smith commented on LOG4J2-16:
--
This concept should also include leverage of
[
https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607124#action_12607124
]
Paul Smith commented on LOG4J2-9:
-
We should consider Spring as part of this configura
On 22/06/2008, at 7:44 PM, Oliver Frietsch wrote:
Hello list,
As there might be differences between 1.2.15 and 1.2.16, I then
checked out the latest 1.2.15 tag from SVN that I could find (/
v1_2_15, there is no 1.2.16!), and tried to build that. This is the
result:
There is ono 1.2.1
type settings to ensure that:
application/x-java-jnlp-file
appears?
cheers,
Paul Smith
On 24/05/2008, at 5:41 AM, Scott Deboy wrote:
The Chainsaw Web Start link no longer launches Chainsaw, it just
displays the jnlp contents.
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsawWebStart
Relating to:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43304
We have already marked the dependencies as optional, and I have
confirmed with the maven-user list this is what we should do.
there is a remaining suggested patch that improves white space layout
and adds specific versio
oddly:
http://people.apache.org/builds/logging/repo/log4j/apache-log4j-receivers/
has a 1.0 and a did have a 1.0-snapshot area. I removed the snapshot
area because I thought it was confusing things but then I realised
that there is no actual 1.0 release just yet.
I'm planning on nuking th
Just returned to work after the birth of our first child (boy,
William, everyone's healthy). Since just before Xmas I've moved
house, had a decent car accident and had a baby, so I've been quite
distracted. Apologies for disappearing!
cheers,
Paul
---
On 12/12/2007, at 5:27 PM, Jacob Kjome wrote:
Paul Smith wrote:
cool, bug found. Now, any consensus on naming patterns? I'd plan
to prefix all thread names with 'log4j-' and use a sensible suffice
depending on the usage (make it aligned with the class name that
laun
ctions I'll try that approach... ?
Paul
On 12/12/2007, at 4:11 PM, Jacob Kjome wrote:
See:
http://issues.apache.org/bugzilla/show_bug.cgi?id=41156
Jake
Paul Smith wrote:
I'm certain there's a bugzilla ticket for this, but even if there
wasn't there should be, but we are the mid
I'm certain there's a bugzilla ticket for this, but even if there
wasn't there should be, but we are the middle of cleaning up thread
names in our app to easily identify their uses, and ran into the
FileWatchdog.
Obviously a consistent pattern of thread names would be good across
log4j th
On 16/11/2007, at 5:37 AM, Curt Arnold wrote:
On Nov 15, 2007, at 4:36 AM, Paul Smith wrote:
Ok, i'm a bit tired, so I ended up just going simple and pretty
much following Curt's idea, see below. Thoughts?
Index: src/main/java/org/apache/log4j/n
That chunk seems just like the IDE at work moving things around.
Honestly, is that really that much of a deal? I agree a total
reformat of the class is not a good idea, but I don't see the need to
get too anal about something like that..
But I didn't see much benefit from hiding t
On 07/11/2007, at 7:15 PM, Curt Arnold wrote:
On Nov 7, 2007, at 1:55 AM, Curt Arnold wrote:
Okay, I'm about ready to fall over, but I looked at zeroconf and
see your motivation for moving the binding onto the main thread so
you continue the set up in
ZeroConfSocketHubAppender.activateO
On 07/11/2007, at 7:15 PM, Curt Arnold wrote:
On Nov 7, 2007, at 1:55 AM, Curt Arnold wrote:
Okay, I'm about ready to fall over, but I looked at zeroconf and
see your motivation for moving the binding onto the main thread so
you continue the set up in
ZeroConfSocketHubAppender.activateO
On 07/11/2007, at 4:06 PM, Will Sargent wrote:
Paul Smith wrote:
Patch against the current code-base attached to a bugzilla issue is
a good start. You should prefix all the source code with the ASL
2.0 license and note in the issue that your are donating this to
the ASF.
After that
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61
I'd like to propose a change to SocketHubAppender code to allow it automatically choose a free port on the local host if the Port property is configured with 0.This will allow the Zeroconf module to be more useful, and allow simpler configuration for multiple applications on the same host. We have
I did push component, receivers, etc to release since I expected
Chainsaw to be pushing for a release and they'd be done
simultaneously. However, there has been no chainsaw commits since
the log4j 1.2.15 release. I think we should at least get the
temporary encoding fix on UTF-8's and w
On 30/08/2007, at 2:36 PM, Curt Arnold wrote:
Vote called 2007-08-25 at 9:58 PM CDT, vote concluded 2007-08-29,
11:35 CDT.
+1 from Curt Arnold, Scott Deboy, Paul Smith
+0 from Jacob Kjome
all PMC members, no other votes.
Proceeding to place releases on distribution servers. Will update
e)
Scott
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne
Hopefully fixed now. The test was picking up NDC content set on a
previous test. Added setUp and tearDown methods that clear the NDC
and MDC before and after the tests. Guess I only ran the test in
isolation.
All looks good now, thanks. I've been burnt by tests like these
myself, n
Right now, with svn updated in log4j/trunk, a 'mvn clean install' fails:
...
[junit] Testcase: testProblemCharacters took 0.016 sec
[junit] Testcase: testNDCWithCDATA took 0.008 sec
[junit] FAILED
[junit] expected:<...> but was:&"' ...>
[junit] junit.framework.ComparisonF
I don't know what possessed me, but I think I've reviewed all the
open log4j bugs today and fixed several of them. I didn't see any
of the other ones that seemed ready for log4j 1.2.15. The big
clusters of bugs seemed to be:
Unless someone wants to lobby for a particular bug, I think I'
Could you refresh me on the technical issue that you are trying to
work around? I looked in the archives and it didn't jump out at me.
I tried googling the original thread I posted about this a while
back, but honestly, I can't seem to find it.
So, here goes. Some Receiver implementatio
em to reach any conclusions, but just seemed to die
out.
Technically you do not need to purchase a code signing certificate.
I already have a Thawte email certificate that allows me to sign code
and it appears as signed by 'Paul Smith <[EMAIL PROTECTED]>" (see
[1]). On initi
Do you think it's worth publishing some of the latest log4j-*
snapshots to the snapshot repo?
http://people.apache.org/repo/m2-snapshot-repository/
Paul
I had a crack at working out how to create 2 separate artifacts for
the log4j-receivers module, 1 for the primary artifact (as current)
and one a chainsaw-specific artifact that excludes the JMS, DB and
VFS-based Receivers. This is needed for the Webstart version because
of the difference
Yes. I'm not using maven at the moment (waiting until this release
gets out). I'll try not to make changes that could break things!
(eclipse's maven support was a bit too confusing for me).
it's different, but it works great for me. Ping me on MSN one day
and I'll help you through it.
To tail via VFS, a version of commons-vfs is required which
provides the fileobject.refresh method (added Mar 30 19:16:24 2006)
According to the Commons-VFS Java API docs, this method is available
in the 1.0 release, so I think that's ok from a Maven point of view.
Did you have any problems
On 09/08/2007, at 3:01 AM, Curt Arnold wrote:
I'd propose:
1. Adding support for properties to XMLLayout, but have it be
disabled by default. Extra elements showing up in content may
disrupt existing applications that consume output from XMLLayout
and shouldn't just appear in a minor r
The eventual goal is to provide a service that can index events using
Receivers and a capable CLI and web interface to search/navigate said
event 'contexts'.
If anyone is interested in feel free to discuss on this or the labs
mailing list.
cheers,
Paul Smith
On 08/08/2007, at 7:22 AM, Curt Arnold wrote:
The log4j 1.2 layout can produce non well formed content for some
atypical content (a message with an embedded -->, threads
containing & or >, etc). Plus it does not output MDC content
(log4j 1.3 does, but shares the other shortcomings). I've
7;m not sure if we should have trunk be a link to 1.2 or abandon it
until 2.0 is viable.
Thought?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Mana
ail [EMAIL PROTECTED] in the web page, tnx.
Thanks,
Sagi Mann
____
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 01:31 AM
To: Log4J Developers List
Subject: Re: JUL appender
New snapshot setup here:
jars:
http://people.apache.o
7/2007, at 4:49 PM, Sagi Mann wrote:
Nice catch!
Thanks for helping out with the investigation.
Could you pls point me to the proper snapshot URL?
Thanks,
Sagi
____
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 06:22 AM
To: Log4J Devel
e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.com
This email and any attachments are inte
On 05/07/2007, at 8:02 PM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote:
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
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.
I don't think we can redistribute activation.jar, jms-1.1.jar,
jmxri-1.2.1.jar, jmxtools-1.2.1.jar and mail-1.4.jar which are
currently included in the generated tarball and zip archive. They
are in the assembly since they are referenced by log4j, but they
can be suppressed.
None o
On 30/06/2007, at 7:15 AM, Curt Arnold wrote:
There is a splash screen that shows Chainsaw history. That should
be integrated into src/changes/changes.xml.
Is this is the Release Notes section you're referring to? Yes I
think tracking the changes in changes.xml is probably best from now
I used the assembly:assembly plug to create a distribution, however
the descriptor (src/assembly/bin.xml) needs to be tweaked to drop
out non-re-distributable jars. Hopefully, all the non-re-
distributable jars are not essential to operation, at least not on
JDK 1.5. Currently, you can d
Hi Curt,
I have not yet worked out how to do this yet, but I thought I'd
mention it before we perform a release of the Receivers module.
Chainsaw will need to be shipped with a cut-down version of the
receivers package due to Classloading rules. The Receivers that
depend on 3rd-party dri
thanks Curt for the rework of the naming and pom. I did a poor job
of copying various files across to that package; my apologise.
You've got a keen eye for detail.
Paul
Online doc: http://logging.apache.org/log4j/companions/zeroconf
Doesn't appear visible to me yet.
--
#48.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
whole
project (they're needed to compile the Receiver).
It's actually not going to be simple as I thought it would to build
this.
Paul
On 25/06/2007, at 5:07 PM, Paul Smith wrote:
http://svn.apache.org/repos/asf/logging/sandbox/jul-to-log4j-bridge/
you'll need maven 2.0.6+
is checked in.
thanks,
Sagi Mann
____
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, June 25, 2007 09:55 AM
To: Log4J Developers List
Subject: Re: JUL appender
I have got the JULAppender (subtle rename, made it upper case to match
the rest of the bridg
?
cheers,
Paul
On 25/06/2007, at 4:42 PM, Sagi Mann wrote:
Thanks for the feedback, makes total sense to me as well.
Sagi Mann
-----Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, June 25, 2007 09:44 AM
To: Log4J Developers List
Subject: Re: JUL appender
O
On 25/06/2007, at 4:32 PM, Sagi Mann wrote:
I have a few questions:
I originally concentrated on ease-of-use as much as possible. I, as
Arnold, am concerned that usage will become overly complex. Current
use is to treat JulAppender as if it was ConsoleAppender (even
replacing any refs to Conso
Answers that I'd be looking for:
Are the log4j->jul and jul->log4j solutions symmetric: For
example, if there is a JULAppender, is there a corresponding
Log4jHandler?
The original bridge code dealt with jul->log4j only. The new
JULAppender code provide by Sagi Mann is the symmetric equ
On 24/06/2007, at 7:03 AM, Curt Arnold wrote:
On Jun 23, 2007, at 11:32 AM, Scott Deboy wrote:
The test case looks fine.
Anyone opposed to me merging this into the 1.2 branch, added to a
new org.apache.log4j.jul package.
Yes, I am opposed at the moment. log4j 1.2.15's release is
i
7, at 3:33 PM, Sagi Mann wrote:
Paul,
'jul' it is. Should I check in under the v1_2branch?
By the way, where can I find info on the bridge project you mentioned?
Thanks.
Sagi Mann
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Fri 6/22/2007 01:04
To: Log4J Developers List
Subject: R
/log4j/branches/
v1_2-branch/
Thanks,
Sagi Mann
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 12:36 PM
To: Log4J Developers List
Subject: Re: JUL appender
This is the correct URL for downloading via svn:
http://svn.apache.org/repos/asf/loggin
e:
+
+$ ssh -l USERNAME people.apache.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, A
On 21/06/2007, at 4:18 PM, Scott Deboy wrote:
I'd still like us to consider finishing the property support
included in LoggerRepositoryEx (mostly requiring new functionality
being added to LoggingEvent). It would make finishing up the
backporting of the appenders & receivers essentially c
I've done the following quick test to compare 1.2.14->1.2.15. After
unpacking both, I compared the contents of the respective jars. One
way to see missing/additional files was this:
unzip -l log4j-1.2.14.jar > /tmp/log4j.1.2.14.txt
..
unzip -l log4j-1.2.15.jar > /tmp/log4j.1.2.15.txt
cat l
Thanks muchly!
On 21/06/2007, at 1:55 PM, Curt Arnold wrote:
On Jun 20, 2007, at 9:10 PM, Paul Smith wrote:
I've been tweaking the jul-log4j-bridge pom to experiment with the
distribution mechanism, and have placed a site and repo sample here:
http://people.apache.org/~p
On 21/06/2007, at 1:27 PM, Curt Arnold wrote:
I've just pushed another release candidate out. This won't be the
last since I forgot to update the release date and another tweak to
the POM that I'd like to do. I'll likely refresh it tomorrow, but
I thought I would leave it up overnight fo
I've been tweaking the jul-log4j-bridge pom to experiment with the
distribution mechanism, and have placed a site and repo sample here:
http://people.apache.org/~psmith/logging.apache.org/
I'm not sure why the source distribution doesn't go with it. Any
ideas appreciated.
Paul
If this was a project proposal, I'd have no issue with you starting
a sandbox project and allow it to develop out in the open.
However, based on your discussion it appears to be pretty far along
and it looks like it should be at least reviewed by the Incubator
PMC before going into Loggi
Hi,
I have been in the background working on a companion to log4j that
I'm initially calling 'pinpoint'. It is designed as a log context
tool to facilitate production queries.
Logging events to a DB for querying is fine, except SQL queries,
IHMO, on that are time consuming and unsatisfyi
t 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: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Sun 6/17/2007 2:42 PM
To: Log4J Developers List
Subjec
umbia 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: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Sat 6/16/2007 10:42 PM
To: Log4J Developers List
Su
Is there any way a thread that creates a LogFilePatternReceiver to
soak in a file of events can be notified or joined onto the Thread
that the Receiver creates to imports the file?
I can't see a way. I was wondering if I could add a small property:
setUseCurrentThread(boolean) , than when
Hmm, while I was mavenizing the Chainsaw site content I was reading
the notes about the VFS, DB and JMS support in Chainsaw again and
realise that right now, Chainsaw is bundling the DB/JMS Receivers in
the maven distribution. Due to hideous classloading rules, they
won't work.
This is b
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
other objects, commit or speak up or risk having to merge later.
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.acone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +6
I'm a bit at a loss to work out how exactly to accomplish this one,
so asking for advice.
The Chainsaw build sort of needs a subset of the log4j javadoc
bundled with it for users to read the Receiver javadoc. I'm not sure
how to declare that with maven.
The only way I can think of is hac
- Chainsaw wouldn't mvn install until I copied known.receivers to
chainsaw/target/classes (was getting an error on the
receivershelpertest)
Fixed it, some resources were still in the java tree, where they
shouldn't have been. Do:
svn update
mvn clean test
It should consistently pass now
Got it all working. A few things:
- getting the log4j 1.2 branch to mvn install was a bit of a hassle
because I needed to get nteventappender.dll into my path (from
1.2.14) - the dll wasn't getting built via mvn install - should it
have been? maybe another maven target I should have looke
Ok gang, mavenization completed I think.
Please grab maven 2.0.4 and install it, and if you use Eclipse,
install the Maven Eclipse plugin:
http://maven.apache.org/
http://m2eclipse.codehaus.org/
After installing the Maven Eclipse plugin, you can activate the
project as a Maven project by d
1 - 100 of 455 matches
Mail list logo
