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:
1) Tomcat shutdown/restart breaking what were intended to be
On Aug 23, 2007, at 12:22 AM, Scott Deboy wrote:
It looks like my most recent commit isn't sufficient. I'll see if
I can improve it before you cut a RC.
-Original Message-
From: Scott Deboy [mailto:[EMAIL PROTECTED]
Sent: Wed 8/22/2007 10:19 PM
To: Log4J Developers List
Subject: R
On Aug 23, 2007, at 1:59 AM, Paul Smith wrote:
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
On Aug 23, 2007, at 12:19 AM, Scott Deboy wrote:
Looks good -
A few things:
1. helpers/Constants.java is in both extras & component. I looked
in helpers for other dups, but didn't see any - not sure if we have
other dups..
Without Constants in extras, TimestampEqualsRule and
Timest
On Aug 23, 2007, at 8:38 AM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Thu Aug 23 06:38:12 2007
New Revision: 568980
URL: http://svn.apache.org/viewvc?rev=568980&view=rev
Log:
Moved Constants out of component & extras
Added application property & remote host now available as
properties v
This change should eliminate the need to provide logger.dtd with no
degradation of behavior (actually should be a tad faster).
On Aug 23, 2007, at 12:07 PM, [EMAIL PROTECTED] wrote:
Author: carnold
Date: Thu Aug 23 10:06:59 2007
New Revision: 569073
URL: http://svn.apache.org/viewvc?rev=569
On Aug 23, 2007, at 12:02 PM, Scott Deboy wrote:
Basically, the reason behind the remotehost and application properties
in 1.3 is to provide the user with an easy way to distinguish between
various event sources (running on one or more machines).
For the 'application' property, users COULD use
Started the process before the mention of the XSLTLayout test
failures on Windows. I've posted rc2 at http://people.apache.org/
builds/logging/log4j/companions/extras/1.0. Jars are also available
in the staging Maven repo at http://people.apache.org/builds/logging/
repo. Any comments are a
I added javamail and activation to the Gump descriptor in my local
copy days ago but forgot to commit it. Hopefully the next Gump run
will be clean.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
log4j 1.2.15 rc6 is available for review at http://people.apache.org/
builds/logging/log4j/1.2.15. rc5 was abandoned during preparation.
I believe this is as good as it is going to get. Corresponding jar
files are also available in the staging Maven repo at http://
people.apache.org/builds
This is a vote on publishing the following artifacts as log4j 1.2.15
and log4j-extras 1.0:
http://people.apache.org/builds/logging/log4j/1.2.15/apache-
log4j-1.2.15_rc6.tar.gz (also .zip)
http://people.apache.org/builds/logging/log4j/companions/extras/1.0/
apache-log4j-extras-1.0_rc5.tar.gz
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
web site tomorrow after releases have had time
PluginConfiguration was getting a little stale relative to 1.2.15's
DOMConfigurator. I could have updated PluginConfigurator or added a
dependency to extras and replaced PluginConfigurator with
org.apache.log4j.extras.DOMConfigurator, however the value of using
component with pre-1.2.15 ve
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
Great!
One thing I notice: the path to Chainsaw is a bit different now.
That's
not a bad thing, but could we redirect the old site & Chainsaw
webstart
link to the new locations?
It wasn't intentional, but looks like I just overlooked the
FYI: There has been a posting with the board's feedback on the issue
of signing Java jars (http://marc.info/?l=incubator-
general&m=118845647414234&w=2).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
Great!
One thing I notice: the path to Chainsaw is a bit different now.
That's
not a bad thing, but could we redirect the old site & Chainsaw
webstart
link to the new locations?
Scott Deboy
Chainsaw downloads should be fixed now. The
On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:
It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html
That is expected. The "new" Maven generated chainsaw content is
below http://logging.apache.org/chainsaw.
On http://logging.apache.org/chainsaw/download.ht
The Logging Services project is pleased to announce the release of
Apache log4j 1.2.15.
Apache log4j 1.2.15 is a maintenance release of log4j 1.2 (http://
logging.apache.org/log4j/1.2).
The list of fixed issues is available at http://logging.apache.org/
log4j/1.2/changes-report.html.
The rele
On Oct 11, 2007, at 7:28 PM, Lilianne E. Blaze wrote:
Hello,
I had major problems getting Log4j compiled on Netbeans 6.0 / WinXP.
It was constantly bitching about lack of NTEventLogAppender.dll, even
when I did everything I could think of to turn off the tests during
compilation.
The patch be
On Oct 11, 2007, at 11:20 PM, Lilianne E. Blaze wrote:
Looks like it's not enough. Is there any simple way to just tell maven
to skip the tests? There is an option in NB that says just that,
but it
doesn't work. Probably having something to do with three different
build
scripts.
For now I
On Oct 12, 2007, at 8:40 PM, Lilianne E. Blaze wrote:
Hello,
Is DOMConfigurator.props (line 127) actually used anywhere? It looks
like it never gets initialized.
Greetings, Lilianne E. Blaze
There is an open bug involving property substitution (http://
issues.apache.org/bugzilla/show_bug.c
On Oct 13, 2007, at 5:57 PM, Lilianne E. Blaze wrote:
Hello,
I wrote a simple patch which makes property resolving pluggable. It
can
be used, for example, to check JNDI env-entries in addition to system
properties, or to specify the priority in which they are resolved
(allowing or disallowin
As far as I recall, the current JMX code was added in one commit long
time ago by a single developer with no preceding discussion about use
cases, design strategies, etc, little or no feedback after it was
introduced and no unit tests. Since it has been present in log4j
releases, the proje
On Oct 30, 2007, at 3:01 PM, Simon Park wrote:
Hi,
I've posted code (Apache license, Log4J coding standards) that I
hope will offer an alternative to the standard Log4J
AsyncAppender. The design intention is to facilitate reduced
blocking for logging operations, thereby allowing higher
ApacheCON US (http://www.us.apachecon.com/) is less than two weeks
away. I'm not going this year (at least at the moment), but have
enjoyed the last 3 ApacheCON US's.
The monthly board meeting is in the middle of ApacheCON and Logging
Services quarterly report is due for the meeting. In t
On Nov 5, 2007, at 2:55 PM, Will Sargent wrote:
Hi all,
I have a layered configurator that I'd like to contribute to log4j,
either as a companion or in the core code. I've read through the
wiki on
http://wiki.apache.org/logging-log4j/ContributingCode
and a description and zip of the co
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.activateOptions. However instead of
changin
On Nov 5, 2007, at 6:55 PM, Paul Smith wrote:
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 configur
On Nov 7, 2007, at 10:22 PM, Will Sargent wrote:
Curt Arnold wrote:
I did take a scan of the code, it does appear to conform to ASF
source header policy (http://www.apache.org/legal/src-headers.html).
It also stated that it was based on log4j 1.3. log4j 1.3
development has been
On Nov 13, 2007, at 8:43 AM, Mak, Howard wrote:
Hello,
I would like to suggest the following changes to
DailyRollingFileAppender. If this is not the appropriate forum for
this email, please direct me to the proper channels as I'm new to
Log4j. ;)
Feature:
- Allow date p
I've logged a bug report (43874) for the SocketHubAppender
enhancement and committed the createServerSocket() patch and updated
the changes.xml for 1.2.16. I'm not saying that has to be the final
approach, but I think there is general agreement that we can do
something minimal and safe in
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/net/SocketHubAppender.java
On Nov 15, 2007, at 2:02 PM, Scott Deboy wrote:
Can we get the maven dependencies corrected so we don't break maven
and
others?
See
http://www.1060.org/blogxter/entry?
publicid=9FDCA6751DE11295AD0049F5DB17
F461&token=
Its fixed in the subversion repo. All that would be necessary is to
On Nov 15, 2007, at 3:35 PM, Paul Smith wrote:
actually I've found a problem with the commit.
If ZeroconfSocketHubAppender class calls super.activateOptions()
which then creates the SocketServer, the actual creation of the
ServerSocket is done by another thread (see the SocketMonitor
con
On Dec 4, 2007, at 3:12 AM, tststs wrote:
I am using log4j for logging. I am working on a huge application and
there
would be lots of logs each day. Thereby it is requried that the log
files be
stored and renamed each day. The date is appended to the log file
and that
day's log file is
On Dec 7, 2007, at 1:12 PM, Paul Duffy wrote:
Folks,
Scenario is app running on multi core hardware at high clock rates.
Millisecond time resolution for LoggingEvent is not going to cut
it. Need a monotonically increasing sequence number in the
LoggingEvent to distinguish order for eve
On Dec 9, 2007, at 11:55 AM, Jess Holle wrote:
Paul Duffy wrote:
For the big picture:
log4j 2.0 intends to target Java 5 and later and follow modern
concurrency best practices, but currently it is only a concept and
some very early experimental code. While I'd love to flesh out
the fra
On Dec 9, 2007, at 11:46 AM, Paul Duffy wrote:
The sequence number that was implemented in log4j 1.3 was
problematic on several fronts. In the implementation in the last
release, the same sequence number could be repeated since it wasn't
guarded with a synchronization block. I believ
On Jan 17, 2008, at 3:28 PM, Paul Smith wrote:
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!
chee
On Jan 20, 2008, at 3:42 PM, Manish Marathe wrote:
Hello All,
Currently the Appender, DailyRollingFileAppender, rolls over the log
file as per the "datePattern" set in the configuration file,
although the rolled-over files never get deleted unlike if we use
RollingFileAppender but in cas
On Jan 28, 2008, at 10:30 AM, Stefan Fleiter wrote:
Hello,
we think that Log4j is missing a possibility to rollover at a fixed
time of the day
and have developed a TimedDailyRollingFileAppender class which does
this.
We would like to contribute the solution to the log4j project.
If ther
On Jan 28, 2008, at 7:54 PM, Jacob Kjome wrote:
I think it would be better to avoid adding a dependency to pick up
the CronExpression since that would likely force the Policy off
into a yet another companion since we would not want to force
everyone who uses extras to pick up quartz.
Why
On Feb 6, 2008, at 9:32 AM, Dominique Laurent wrote:
Hi,
Just to let you know that the manifest (MANIFEST.MF) in
log4j-1.2.15.jar uses:
Name: org.apache.log4j
instead of
Name: org/apache/log4j/
Note the dot '.' instead of the slash '/'.
It means that the following piece of code:
On Feb 9, 2008, at 11:05 AM, Katherine Hale wrote:
Hello! I have checked out the sandbox via SVN, I'm familiar with ANT
& test cases and all that good stuff. The readme said I should post
here to contribute. If anyone wants to send me information about
exactly where to submit a contributio
On Feb 10, 2008, at 8:35 PM, Katherine Hale wrote:
Curt -
Thanks for the fly-by-night introduction. This is what I was
thinking in more detail. Again I know this is Java 5, so this would
be for Log4J 2.0, although perhaps something comparable could be
devised for the current Log4J. I'll
On Feb 20, 2008, at 4:14 AM, Stefan Fleiter wrote:
Hello Curt,
[Offer to provide TimedDailyRollingFileAppender or
CronExpressionFileAppender]
Thanks a lot for your answers and four your Pointing to the
companions.
I do not think that this is the right place for such a
functionality, th
I've logged a Infrastructure request (https://issues.apache.org/jira/browse/INFRA-1559
) to create a new JIRA project for log4j 2.0 development. Initially,
it would be used to gather requirements and document the development
decisions. I would not expect the request to be controversial.
H
I sorry that I haven't had time to look at your proposal but hope to
on Monday.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On May 16, 2008, at 9:01 AM, Jess Holle wrote:
I grabbed the 1.2.15 sources, built them, and then tried to run the
regression tests -- in preparation for making changes and then
verifying no tests fail.
Unfortunately, I get the following failure:
Minimum:
[junit] Running org.apache.log
On May 19, 2008, at 10:22 AM, Jess Holle wrote:
Jess Holle wrote:
Thanks.
I'm also starting to ponder whether there's a mostly compatible way
to reduce locking in AppenderSkeleton and WriterAppender.
For instance, we could add a special Layout interface that would
allow the String to be
On May 19, 2008, at 11:22 AM, Jess Holle wrote:
If it is sufficiently compelling it appears it would be possible to
rework AppenderSkeleton without breaking most extensions thereof but
allowing Layout.format() to be hoisted out of the synchronization
block in cases where the Layout is an in
On May 20, 2008, at 4:19 AM, Jess Holle wrote:
Curt Arnold wrote:
On May 19, 2008, at 11:22 AM, Jess Holle wrote:
If it is sufficiently compelling it appears it would be possible
to rework AppenderSkeleton without breaking most extensions
thereof but allowing Layout.format() to be
I'm travelling at the moment and don't have the tools to track this
down. I'd assume the problem is the wrong mime type is being sent. If
so, that could be tweaked in the .htaccess file in the same directory
and would not require escalation to infra.
---
I've added a .htaccess file to that directory. When the main public
servers resync, it should start delivering the expected MIME type.
Why the MIME type changed (if it did) not known.
On May 25, 2008, at 5:09 PM, Paul Smith wrote:
Hi friendly and stretched infrastructure people's. Has t
On May 23, 2008, at 2:41 PM, 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.jnlp
I don’t think there’s anything we can do on our site, correct?
Bring t
On Jun 5, 2008, at 7:19 PM, Jess Holle wrote:
For my own usage I went ahead and completed the a set of changes to
reduce log4j 1.2.x's locking and deadlock potential. The results
are attached and make unabashed use of Java 5 -- as from discussion
to this point it seems clear that there is
The "Copyright The Apache Software Foundation" style header is
obsolete. Any new releases need to use the "Licensed to the Apache
Software Foundation..." style header. See http://www.apache.org/legal/src-headers.html
On Jun 6, 2008, at 1:18 AM, [EMAIL PROTECTED] wrote:
Author: sdeb
On Jun 6, 2008, at 11:53 AM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Fri Jun 6 09:53:52 2008
New Revision: 664032
URL: http://svn.apache.org/viewvc?rev=664032&view=rev
Log:
Update ASL headers
That is disturbing. Did we not catch the old headers when we released
apache-log4j-extras
On Jun 11, 2008, at 12:57 PM, MrNobody wrote:
In the property file I can set a particular package or class to have
DEBUG
level, despite what my overall logging level is, like this:
log4j.logger.com.ibatis=DEBUG
How do I do this programatically - (in the code, not in property
file) ???
On Jun 19, 2008, at 1:35 AM, Ralph Goers wrote:
The website says there is an experimental branch for log4j 2.0
development, but I can't seem to find it.
I did some experiments a year ago in http://svn.apache.org/repos/asf/logging/sandbox/experimental/pattern-layout
that capture several of
ntenance tasks for log4j 1.2 around would also allow log4j 2.0 to
proceed faster.
Ralph
Curt Arnold wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm not going to have any development time next week, but hope to move
some things around tomorrow to get started with log4j 2.0. My plan is
to add a 2.0 branch (logging/log4j/branches/2.0) with a overall
project pom.xml with log4j2-core (initially the pattern-layout sandbox
experiment) an
On Jun 21, 2008, at 3:56 AM, Serkan Kaba wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently log4j depends on jmx RI and can't be compiled with jmx that
comes with Java>=1.5. Recently Sun stopped distributing sources of JMS
resulting in Gentoo packages for jms and log4j breakage. Ca
After a vote on the PMC private list, Ralph Goers has been granted
commit access to the log4j 2.0 branch.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Jun 29, 2008, at 6:55 AM, Oliver Frietsch wrote:
---
Test set: org.apache.log4j.TestLogMF
---
Tests run: 116, Failures: 2, Errors: 0, Skipped
On Jul 3, 2008, at 6:06 PM, Scott Deboy wrote:
log4j-receivers-3rdpartydeps?
pretty hokey but a bit more accurate
The first thing that makes me think of is the third party licensing
policy (http://www.apache.org/legal/3party.html) and suggests use of
code that is not under the ASL. I'm
On Jul 4, 2008, at 12:28 PM, Thorbjørn Ravn Andersen wrote:
Paul Smith skrev den 04-07-2008 02:02:
I think that there should be a core log4j which should cover those
classes described in the printed manual, and that all the other
stuff which has come up since then should go in one or m
On Jul 5, 2008, at 1:27 AM, Scott Deboy wrote:
When does the previous version of Chainsaw get taken out of log4j jar?
Earlier this week I responded to questions about how to configure
Chainsaw to use receivers. It turns out he was using the old
version of Chainsaw.
Would be nice to avoi
On Jul 21, 2008, at 10:16 PM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Mon Jul 21 20:16:25 2008
New Revision: 678623
URL: http://svn.apache.org/viewvc?rev=678623&view=rev
Log:
changed logfilepatternreceiver parsing to use .*? and .* instead of .
+? and .+
allows use of empty string mat
On Aug 5, 2008, at 4:52 PM, Paul Smith wrote:
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.
I was trying to preserve the external beh
On Aug 5, 2008, at 5:22 PM, Paul Smith wrote:
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 with
On Aug 5, 2008, at 5:28 PM, Paul Smith wrote:
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 c
On Aug 5, 2008, at 5:28 PM, Paul Smith wrote:
On a related note, I notice that there is movement to use JIRA for
log4j2 (yay!). I know it's a personal view of many to keep things
'free', but honestly I find fighting with Bugzilla an absolute PITA,
and I'd really just like to focus on what
I'd like to address the following bugs and then get an RC1 for log4j
1.2.16 out
https://issues.apache.org/bugzilla/show_bug.cgi?id=37638
https://issues.apache.org/bugzilla/show_bug.cgi?id=44157
https://issues.apache.org/bugzilla/show_bug.cgi?id=44386
https://issues.apache.org/bugzilla/show_bug.
On Aug 13, 2008, at 4:27 AM, Thorbjørn Ravn Andersen 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 bytecode.
Th
On Aug 13, 2008, at 5:34 PM, Paul Smith wrote:
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 late
log4j-dev is likely the best place for the discussion, just sometime a
discussion never catches fire for some reason. Given your initial
post was in August, vacations are a likely culprit.
How do you propose accessing the FileWatchdog instance to interrupt
it? Looking at DOMConfigurator a
On Aug 15, 2008, at 7:15 PM, Paul Smith wrote:
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:
...
On Sep 5, 2008, at 2:49 PM, Chad LaVigne wrote:
I sent this message regarding a code contribution a little over a
week ago and haven't received any feedback. Is this still the
correct mailing list for contributions?
Yes, but entering it in Bugzilla (http://issues.apache.org/bugzilla)
This is intentional. log4j-extras needs the interface definition
since it may work with versions of log4j prior to log4j 1.2.15. log4j
1.2.15 needs the definition since it calls the
UnrecognizedElementHandler when it encounters an unrecognized element.
On Sep 12, 2008, at 1:28 AM, Paul S
Can't make ApacheCon this week in New Orleans? You can still watch all
the keynotes, Apache 101 sessions, and system administration track in
live video streams:
http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann
Keynotes and the Apache 101 lunchtime sessions are free; the full
On Dec 3, 2008, at 5:41 AM, Ceki Gulcu wrote:
Hello,
As you are probably aware, more and more projects are adopting the
SLF4J API. I would venture say that SLF4J's adoption rate is roughly
equivalent to that of log4j itself. Although the SLF4J API is not
perfect, most SLF4J users seem to be
On Dec 4, 2008, at 6:26 AM, Ceki Gulcu wrote:
Hello Ralph,
Thank for you for your reply. Logback as the basis for log4j 2.0 is a
larger step than what I had in mind. Implementation of the SLF4J API
directly in log4j is a low-hanging fruit but having a significant
positive impact on the java co
On Dec 9, 2008, at 4:58 AM, Thorbjørn Ravn Andersen wrote:
There was a request recently to make the argument replacement
mechanism more powerful in either slf4j or logback (cannot remember)
where Ceki mentioned that one of the major benefits of the {}-
approach was that it was measurably fas
On Dec 10, 2008, at 11:36 AM, Ceki Gulcu wrote:
Curt Arnold wrote:
The supposed performance benefit of the SLF4J formatter over the
java.text.MessageFormat only occurs when you compare the
performance against naive use of java.text.MessageFormat. LogMF
handles the simplest pattern
On Dec 11, 2008, at 9:04 AM, Ceki Gulcu wrote:
On Dec 9th 2008 16:57 GMT Curt Arnold wrote:
> The supposed performance benefit of the SLF4J formatter over the
> java.text.MessageFormat only occurs when you compare the performance
> against naive use of java.text.MessageForma
On Dec 12, 2008, at 9:01 AM, Ceki Gulcu wrote:
True. I'll get the ball rolling so that you will have code to look
at.
[1] http://bugzilla.slf4j.org/show_bug.cgi?id=116
Please use ASF resources for log4j related development. All
development needs to be done in public in community or it m
On Dec 13, 2008, at 3:09 AM, Ralph Goers wrote:
On Dec 12, 2008, at 11:59 PM, Scott Deboy wrote:
Which logback features? Are they a part of SLF4j's API?
A combination. I needed Markers and I've added some minor stuff to
the SLF4J extensions. What I really needed were the TurboFilters i
Sorry about being a little slow to respond recently, but I've been
working on wedding plans. Julie Ferguson and I are marrying in New
Braunfels, TX on December 27th. Julie and I have known each other a
little over 6 years as friends and we kept in touch infrequently after
she moved away f
On Jan 7, 2009, at 9:27 AM, Luciano Izquierdo wrote:
Hi, i have a problem, and i want know if somebody can i help me.
I have two appenders
Appender1
And
Appender2
And have one logger
Logger1
I want to do, that all messege debug, info, warn, error and fatal,
will
write in de appe
On Jan 8, 2009, at 6:24 AM, Luciano Izquierdo wrote:
Hi, thanks for your answer.
But your solution is if I will have only two appenders.
That does not serve me because I have more than two appenders, then
if I
change the root logger, the others appenders and loggers can be
broken.
I need a
On Feb 3, 2009, at 2:46 AM, Zhao, Frank wrote:
Hi,
Can anyone of you help me resolve below issue?
I am using apache-log4j-1.2.15 and apache-log4j-extras-1.0.jar. here
is the error message.
16:04:59,801 INFO [WebService] Using RMI server codebase:
http://localhost:8083/
16:04:59,817 INFO
Long overdue. Was hoping to get it out in September of last year, but
Hurricane Ike ruined the plan. Been traveling incessantly since
November, but am back home now and hope to be able to get to it shortly.
On Feb 28, 2009, at 10:40 AM, Oleg Sukhodolsky wrote:
Hi,
I wonder if there any
If you have a bug that you'd really like to see integrated and there
is an available patch or the solution isn't a totally rearch of log4j,
please speak up. I hope to cut a release candidate this week. Will
try to make a sweep through the open bugs for ones that can be
resolved, but might
On May 12, 2009, at 5:36 AM, Stefan Fleiter wrote:
Sorry, I have to correct myself:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44308
This bug contains a patch for JMX Management of Log4j Appenders and
their log levels.
The levels of *loggers* can be configured.
Sorry hadn't foll
On May 13, 2009, at 6:19 AM, Jess Holle wrote:
Curt Arnold wrote:
Sorry hadn't followed that one. It seems like a good replacement
for some not ready for primetime code that has been in log4j for a
while. However, since it is all new code and not any modifications
to existing
Should update the FAQ since it still mentions log4j 1.3 which has been
discontinued.
The target parameter indicates the byte-code format to be generated in
the compile step. It implies the minimum JRE revision below which
loading is prohibited. It does not indicate the suggested,
recomm
There was discussion a few years back that was spread across several
mailing lists on localization of logging, see http://article.gmane.org/gmane.comp.jakarta.commons.devel/59103/
for a jumping off place. Searching for "localization" on the
mailing list has two many false hits on Gump messag
On Jul 10, 2009, at 4:43 PM, bugzi...@apache.org wrote:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44386
taohuang.t...@gmail.com changed:
What|Removed |Added
We've discussed the javac target option previously, setting target=1.2
does not indicate that only methods in the JDK 1.2's class library are
used, it means to output byte-code that adheres to that particular
JVM's byte code format. The target setting was intentional. I'm not
aware of any
1 - 100 of 772 matches
Mail list logo
