On May 7, 2012, at 2:20 PM, Gary Gregory wrote:
Hi All:
Because I could not get the full build to run on Windows 7 with Maven 2 or 3.
I feel reluctant to VOTE +1 here. This is a know issue due to the use the GNU
app Winres. I get bits and pieces of the build to work but nothing like the
is required is required packaging work to explicitly
exclude classes which I didn't pull in to the PBP-compatible version
(primarily db-related appenders, JMS, etc).
I could essentially provide this as a patch plus an updated build target.
Scott
On Tue, Oct 18, 2011 at 10:02 PM, Curt Arnold
On Oct 18, 2011, at 3:34 PM, Scott Deboy wrote:
I have been given permission to provide our tru2way changes to get log4j 1.2
to work on personal basis profile 1.1, if anyone wants them (core and extras
and some other tweaks like pulling in the logSF helpers in to the logger
class)...so I
On Oct 18, 2011, at 5:12 PM, Scott Deboy wrote:
I would like to see much of what is in extras and component (at least
functionality-wise) be rolled in to log4j 2. If it's in Chainsaw I really
doubt that will happen. If it's in extras it may happen but I still doubt it.
My preference
On Oct 10, 2011, at 3:23 AM, Christian Grobmeier wrote:
Moving component and receivers to core would be more work given the
peculiarities of the tests. It took a couple of hours just to move the
Rewrite appenders and their tests.
Because why exactly? I thought it could be done with svn
This should be the final nag on receivers. I've removed it from Gump's profile
given the clear direction that it will be going somewhere else. I also tweaked
Chainsaw's Gump profile to drop its dependencies on receivers which will
hopefully get it building on Gump again.
On Oct 11, 2011, at
On Oct 9, 2011, at 10:34 PM, Scott Deboy wrote:
Can we drive to a resolution on this issue? Does this require a vote? I'd
like to do something to get the receivers and component code and Chainsaw out
of purgatory. I would prefer to either pull receivers and component in to
core (since
I used Nexus for the last release of log4j and struggled with it. If I remember
correctly there were issues with our Maven group ID not starting with
org.apache that prevented the release from being mirrored to Maven central, but
think we finally worked through all the issues.
I would not be
Been lurking and watching the thread, wanted to throw some comments out without
fully following the thread. Take everything with a grain of salt.
log4j 1.2's AsyncAppender does a bit of this by calling all sorts of methods to
force the lazy initialization of the event prior to the event being
Forget the packaging renaming bit. No need to make Chainsaw an OSGi package and
no need to add additional work.
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail:
On Sep 1, 2011, at 6:13 AM, Christian Grobmeier wrote:
Scott,
Curt had an interesting idea lately, he mentioned it might make sense
to move the companions code into chainsaw.
What do you think on that?
I like the idea - less releases, and no other interested parties in
having
The SVN commits have been redirected and will no longer go to the -dev lists
(or gene...@logging.apache.org for Chainsaw).
On Aug 25, 2011, at 10:49 PM, Curt Arnold wrote:
The comm...@logging.apache.org mailing list is now accepting subscription
requests at commits-subscr
On Aug 26, 2011, at 1:38 PM, Christian Grobmeier wrote:
Pulling old Chainsaw and lf5 out of core would have probably made up for the
difference..but hey, that ship has sailed...maybe they could all be pulled
into extras (component and receivers?)
You mean, move the code from component and
The comm...@logging.apache.org mailing list is now accepting subscription
requests at commits-subscr...@logging.apache.org. The current plan is to
redirect all SVN commit messages from logging services projects to
comm...@logging.apache.org and to discontinue any commit message logging to
We've supported both building with either Ant or Maven for many years, though
releases have been exclusively Maven for a while. The Ant build and test
scripts were necessary to build and test on JDK 1.3 and earlier (which also
required an earlier version of Ant, though I forget the specific
On Aug 26, 2011, at 12:12 AM, Curt Arnold wrote:
We've supported both building with either Ant or Maven for many years, though
releases have been exclusively Maven for a while. The Ant build and test
scripts were necessary to build and test on JDK 1.3 and earlier (which also
required
This following patch would kill building NTEventAppender.dll which has been
included in the distribution for the last couple releases (after being missing
for several releases). There were several emphatic requests prior to the
previous releases to also provide an x64 version of NTEventAppender
I didn't see any commit messages for these revisions which I likely means that
Christian isn't subscribed to the log4j-dev list using grobme...@apache.org and
the commit messages from SVN got bounced by the mailing list. I checked the
status on the request for comm...@logging.apache.org and it
On Aug 18, 2011, at 11:35 AM, Christian Grobmeier wrote:
I think the main reason for antrun is to enhance the generated site
afterwards, and probably for publishing.
Most other stuff can be done with maven, so I would give my +1 to
reduce the Ant dependency to a minimum - again.
Imho
Receivers depends on Component, so I would think Component would be the first
to push.
On Aug 16, 2011, at 5:30 AM, Christian Grobmeier wrote:
Chainsaw needs a companions release - which one exactly?
Now the poms are in a ok state, means they are cleaned up but not
100% functional. Now
This weekend I was able to reassembly my home office after moving last month.
I had hoped to do more catching up, but only got as far as assembling the
quarterly board report and writing this message.
It was encouraging to see the discussions in the bug reports in mid-April
around
It would be a good time to get it in as a release is long overdue and a small
low risk patch could go in pretty easily.
Alternatively, you could write a custom ThrowableRenderer and configure log4j
to use it. Your throwable renderer could delegate to EnhancedThrowableRenderer
and then just
See the LogMF or LogSF classes. LogMF used MessageFormat type format
specifiers ({1}) while LogSF uses SLF4J format specifiers ({}) .
varargs were introduced in Java 5 and have an unavoidable array
construction/destruction expense even if the level is not reached. The LogMF
and LogSF classes
I believe that the behavior is designed to mimic the logic of the filter's in
AppenderSkeleton. If no filter either chooses to accept or deny the request it
is assumed to be accepted. If the desired behavior is to deny any request that
is not explicitly accepted or denied, then the last
On Mar 7, 2011, at 12:48 AM, Christian Grobmeier wrote:
Are there any news or is extras still not released?
It did finally hit the Maven Central repository, though it took a couple of
iterations and looks like it occurred on 2011-01-08. I thought that I had
mentioned around the time that
Could you provide some background on the use of the org.slf4j namespace in the
commit?
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
The easiest way would be to write your own Layout that delegates to
encapsulated layouts (possibly instances of PatternLayout or
EnhancedPatternLayout) depending on the level. Log parsing tools would likely
be baffled by formats that change every logging event, so you might want to
design
On Jan 5, 2011, at 8:23 AM, Ralph Goers wrote:
I'm not ignoring these, just looking for a good way to benchmark the
performance.
Ralph
I've redirected the nag emails so they go to you personally and not the list.
Remember that we need to change it back when the tests become stable
Thanks for the report and patch. Creating a new bug would be better. Patch
looks good on a first visual check.
On Dec 10, 2010, at 3:11 AM, Louis Jacomet wrote:
Hi all,
I recently investigated a deadlock happening inside our JBoss AS.
I tracked down the root cause to the AsyncAppender
On Dec 10, 2010, at 3:32 AM, Peter Szanto wrote:
Hi Jake and Ralph
I submitted the updated version of JDBC Appender to bugzilla to here:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50366
Is there anything else I should do?
Thanks
P
There does not seem to be any patch or
Been slowing working to get Extras 1.1 to the Maven central repo. The repo
sync process is different now. Had to file a JIRA issue for
http://repository.apache.org to have a spot set up for log4j, then figure out
how to get our already built artifacts to the Apache staging repo (create a jar
/browse/INFRA-3214). Currently waiting for a
resolution or assistance to move extras 1.1 to Maven repo.
On Nov 19, 2010, at 11:29 PM, Curt Arnold wrote:
Vote closed, Nov 19th, 11:30 PM (CST). Vote open 98 hours, 3 +1 from PMC
members (Curt Arnold, Scott Deboy, Christian Grobmeier). No other
Vote closed, Nov 19th, 11:30 PM (CST). Vote open 98 hours, 3 +1 from PMC
members (Curt Arnold, Scott Deboy, Christian Grobmeier). No other votes.
Release approved.
I will proceed to move release artifacts to www.apache.org/dist and Maven sync
repo. Will update site after release hits
Take 4.
New artifacts have been uploaded.Signed with my key 70C9C3D0, created
2010-02-17. Change file has an anticipated release date of November 19th.
Vote will be open at least 72 hours unless pulled.
On Nov 13, 2010, at 2:53 AM, Curt Arnold wrote:
I've prepared a release candidate
with the
tarballs, so do you mind cutting another release candidate?
Thanks
Scott
On Sat, Nov 13, 2010 at 12:53 AM, Curt Arnold carn...@apache.org wrote:
I've prepared a release candidate for review and voting. The artifacts can
be downloaded from
http://people.apache.org/builds
I've prepared a release candidate for review and voting. The artifacts can be
downloaded from
http://people.apache.org/builds/logging/repo/log4j/apache-log4j-extras/1.1.
The staged documentation can be viewed at
Reporter: Curt Arnold
All Apache projects are to bring their sites into conformance with the Apache
Project Branding requirements (http://www.apache.org/foundation/marks/pmcs) by
Q1 2011.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
I worked several hours on preparing the extras companion for release today,
specifically around the new Apache Project Branding requirements
(http://www.apache.org/foundation/marks/pmcs). I made some progress, but fell
short of completing.
Among the issues:
Consistent letter case for log4j.
I think I have the build problem for extras fixed. I'd like to resolve your
right truncation feature and get a release candidate built tomorrow night. I
haven't build receivers or chainsaw for a while, hopefully they are problem
free. Both of those likely require more vetting since we
Isabella Claire Arnold was born on September 14th at 1:55 PM. Mom is a little
sore and daughter is getting a little extra oxygen and IV feeding, but is
expected to be on her own soon.
-
To unsubscribe, e-mail:
On my to-do list for the long weekend.
On Sep 4, 2010, at 10:56 AM, Scott Deboy wrote:
I've wrapped up all of the Chainsaw changes I want to include in this
release. Any feedback would be welcome.
Current tarball and DMG available here: http://people.apache.org/~sdeboy/
Now it's time
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893924#action_12893924
]
Curt Arnold commented on LOG4J2-41:
---
I agree that most urges to use extensible levels
I've quickly looked at this and am not quite sure what is going on. The Gump
report says it has been in this state since 2010-07-05T00:00, so typically
you'd look for some change in either Chainsaw (none know of) or a dependency
(in this case likely VFS) in a 24 hour window before that,
On Jul 1, 2010, at 12:11 AM, Scott Deboy wrote:
I actually don't have a pgp signature on file here, so I don't think I can
cut release candidates myself without going through some hoops, so I've been
relying on Curt's free time, but I should probably just figure out what I
need to do to
On Jun 19, 2010, at 2:44 AM, Scott Deboy wrote:
As of svn 956915, rat plugin was added to all pom files, and I've added
licenses to all required files. Log4j still has an issue in its rat config
(output folder is causing the ant:check maven task to fail)
Scott
Fixed the rat check issue
On Jun 7, 2010, at 11:39 PM, Scott Deboy wrote:
I think we'd be ok either way..UnrecognizedElementHandler is in
component...and I could see someone needing that.
I have one Chainsaw feature I've implemented that I don't know if I want to
commit (displaying the time deltas between events
I've been doing some prep work to get the companions ready for a release in
anticipation of a Chainsaw release push. I saw that there are still Javadoc
issues in receivers, but as far as I know there is nothing that would prevent
preparing release candidates other than trying to get OSGi
Ralph Goers has been elected to join the Logging Services Project Management
Committee. Ralph is an Apache Software Foundation member and is also member of
the Attic, Cocoon, Portals, Excaliber, Incubator and Maven PMCs. Ralph has
recently contributed to the log4j 2.0 sandbox and has
On Jun 5, 2010, at 9:27 AM, Ralph Goers wrote:
WTF? I checked that class in? I haven't even finished it.
Please don't feel something has to be finished to be checked in, otherwise no
one would be able to comment until things were already set. Compiling is nice,
but not essential. If you
On Jun 5, 2010, at 9:27 AM, Ralph Goers wrote:
WTF? I checked that class in? I haven't even finished it.
By the way, looks like Gump is now building the log4j 2 sandbox. I had made a
shot of it last weekend, but forgot to press Save on my editor and committed an
unchanged copy of the
Components: API
Reporter: Curt Arnold
On May 30, 2010, at 11:49 AM, Thorbjørn Ravn Andersen wrote:
There is one more thing that I would really like to see in log4j 2.0, namely
the ability for a servlet to log to a servlet container using log4j (and in
slf4j too but that is a different
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874415#action_12874415
]
Curt Arnold commented on LOG4J2-41:
---
Both java.util.logging and log4j 1.2 support user
On May 31, 2010, at 1:57 PM, Ralph Goers wrote:
On May 30, 2010, at 2:53 PM, carn...@apache.org wrote:
Author: carnold
Date: Sun May 30 21:53:24 2010
New Revision: 949590
URL: http://svn.apache.org/viewvc?rev=949590view=rev
Log:
Code review comments
Added:
On May 31, 2010, at 3:28 PM, Thorbjørn Ravn Andersen wrote:
Den 30/05/10 23.12, Curt Arnold skrev:
I don't have this in code or in the JIRA, but I have mentioned in recent
threads the idea of a user-supplied context object in logging calls.
Currently log4j has a thread associated context
On May 31, 2010, at 6:56 PM, Ralph Goers wrote:
On May 31, 2010, at 3:53 PM, Curt Arnold wrote:
On May 31, 2010, at 3:28 PM, Thorbjørn Ravn Andersen wrote:
Den 30/05/10 23.12, Curt Arnold skrev:
I don't have this in code or in the JIRA, but I have mentioned in recent
threads
On May 30, 2010, at 11:49 AM, Thorbjørn Ravn Andersen wrote:
There is one more thing that I would really like to see in log4j 2.0, namely
the ability for a servlet to log to a servlet container using log4j (and in
slf4j too but that is a different story). Currently that cannot be done,
[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873295#action_12873295
]
Curt Arnold commented on LOG4J2-10:
---
A few resources from browsing, haven't processed them
Support getLogger(Object)
-
Key: LOG4J2-37
URL: https://issues.apache.org/jira/browse/LOG4J2-37
Project: Log4j 2
Issue Type: Task
Components: API
Reporter: Curt Arnold
Suggested at http
On May 26, 2010, at 11:01 PM, Ralph Goers wrote:
I'm not sure what the appropriate way to respond to all the comments is going
to be. Some of them I agree with and will make changes when I get the chance.
Many of them just need an explanation or I disagree with the comment - not
sure what
On May 27, 2010, at 5:55 AM, Ralph Goers wrote:
I know you mentioned getting git set up.
Raised it with infrastructure at
https://issues.apache.org/jira/browse/INFRA-2743, part of the response was:
To create and checkout a local log4j2 branch that tracks the remote
On May 24, 2010, at 12:08 PM, Thorbjørn Ravn Andersen wrote:
Den 24/05/10 08.54, Ralph Goers skrev:
BTW - If I didn't say it before, this is the one place that git would be
helpful. You could fork the code and do what you like and I could merge
back what I like, etc. I don't really find
Appender interface should be refactored
---
Key: LOG4J2-36
URL: https://issues.apache.org/jira/browse/LOG4J2-36
Project: Log4j 2
Issue Type: Wish
Components: Appenders
Reporter: Curt
[
https://issues.apache.org/jira/browse/LOG4J2-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871004#action_12871004
]
Curt Arnold commented on LOG4J2-36:
---
Layout should be part of the Channel since some
On May 23, 2010, at 2:27 AM, Ralph Goers wrote:
On May 22, 2010, at 8:13 PM, Curt Arnold wrote:
On May 22, 2010, at 10:50 AM, Ralph Goers wrote:
Also, I have had an issue where the I wanted the toString() method on the
object to be logged to be delayed as much as possible
I'm prepping to start diving into the recent code drop and trying to figure out
how to do so in an effective way. I was thinking maybe the best way to
approach it would be to use annotations or javadoc to make comments on the
classes or methods. This fairly old article
On May 21, 2010, at 11:15 PM, Ralph Goers wrote:
1. I first created an API that had the features I was looking for. That is
in log4j2-api. While it supports logging a String or an Object it really
uses a Message interface which is valuable as it allows users to log
self-describing
On May 22, 2010, at 10:50 AM, Ralph Goers wrote:
Also, I have had an issue where the I wanted the toString() method on the
object to be logged to be delayed as much as possible (somewhat helped with
the {}-construct in slf4j). This might be doable with a specific log
interface.
Thought it might be best to leave the old thread behind, hope nobody minds.
On May 14, 2010, at 2:22 AM, Ralph Goers wrote:
Thanks for trying it out. I hadn't actually built from the root - I've built
the api and core separately - so I'm glad you were able to fix those problems.
I didn't
On May 17, 2010, at 3:24 AM, Jukka Zitting wrote:
Hi,
As suggested by Sander Temme [1], how about using svn propset
--revprop -r 943816 svn:log '...' to update the commit message of
this revision? Having Ralph's extended summary included in the svn
history would be much better than just
On May 17, 2010, at 9:11 AM, Ralph Goers wrote:
I haven't dug into it, but I think the submission may require IP clearance
through the incubator (http://incubator.apache.org/ip-clearance/index.html).
The sentence would appear to apply:
Any code that was developed outside of the ASF
have cycles to help get companions out the door if
needed.
Anything I can help with?
Scott
On Tue, May 4, 2010 at 7:16 PM, Curt Arnold carn...@apache.org wrote:
Need to back port some of the later fixes in the log4j 1.2.16 release back
into the extras companion. Other than that I
Could you review the bugs in the log4j2 JIRA and give a quick comments about
your submission and the bug.
If there are any significant design decisions or requirements that came out
from this work, could you file them as new bugs.
Did you use or consider the earlier pattern layout stuff I did
On May 14, 2010, at 8:41 PM, Ralph Goers wrote:
See below.
On May 14, 2010, at 7:07 AM, Curt Arnold wrote:
Could you review the bugs in the log4j2 JIRA and give a quick comments
about your submission and the bug.
Sure. I'll try to do this asap but my time to work on Log4j isn't very
log4j2-api/pom.xml has a stray /build (see patch following). Also, the
master pom in BRANCH_2_0_EXPERIMENTAL/rgoers expects log4j2-docs to be in the
same directory, when it is currently located one directory closer to root.
After those changes, I was able to run mvn test/
I haven't had a
Need to back port some of the later fixes in the log4j 1.2.16 release back into
the extras companion. Other than that I don't know of anything.
I've got some evenings free later this week and was going to try to clean up
some post 1.2.16 issues.
On May 4, 2010, at 12:04 AM, Scott Deboy
Vote was open for more a little less than 4 days. +1 from Curt Arnold, Scott
Deboy, Jacob Kjome, all PMC members, No other votes.
mailto:carn...@apache.org wrote:
The log4j-1.2.16-javadoc.jar included in the log4j 1.2.16 release
vote was found to be missing META-INF/LICENSE
log4j 2 should be modular
-
Key: LOG4J2-34
URL: https://issues.apache.org/jira/browse/LOG4J2-34
Project: Log4j 2
Issue Type: Wish
Reporter: Curt Arnold
See
http://mail-archives.apache.org/mod_mbox
The log4j-1.2.16-javadoc.jar included in the log4j 1.2.16 release vote was
found to be missing META-INF/LICENSE and META-INF/NOTICE before it was
distributed. I've prepared a variant by extracting the original jar, adding
the missing files, removing the stray .svn directories and repackaging.
On Apr 6, 2010, at 9:55 PM, Brett Porter wrote:
On 07/04/2010, at 12:41 PM, Curt Arnold wrote:
I've copied the .zip and .tar.gz to the master distribution site and then
out to the mirrors.
While investigating the new procedure to push releases out to the Maven
master repo, I saw
On Apr 7, 2010, at 5:22 PM, Brett Porter wrote:
Fixing it right would require either changing the Maven plugin or adding
steps in our build to correct it after it is built and should be done for
1.2.17.
Are you saying the Maven default javadoc build included .svn? I've never seen
that
A belated +1 from me.
Vote was open for 6 days, +1 votes from Scott Deboy, Christian Grobmeier, Jacob
Kjome and Curt Arnold (all PMC members), no other votes.
Closing vote and proceeding to post the release.
On Mar 31, 2010, at 12:11 AM, Curt Arnold wrote:
I have posted a third release
I have posted a third release candidate for log4j 1.2.16. RC1 was scuttled in
February since I was not aware of the new signing key policy until I was ready
to sign the release. RC2 was scuttled on Sunday since I put the wrong
prospective release date.
The vote is on the following artifacts:
A first release candidate for Apache log4j 1.2.16 can be downloaded from
http://people.apache.org/builds/logging/repo/log4j/log4j/1.2.16/log4j-1.2.16.tar.gz
(md5: f88f322d38b9a51fec79b43fb5e3b3e1)
http://people.apache.org/builds/logging/repo/log4j/log4j/1.2.16/log4j-1.2.16.zip
(md5:
I've cleaned up the test code and have been able to complete mvn test with
current Sun, gcj, openjdk, and Apache Harmony JDK's on Linux. Haven't tested
Oracle, IBM or tested with earlier JDK's on this iteration.
If you have a favorite JDK that is not represented, please give it a whirl and
if
On Mar 27, 2010, at 7:41 PM, Scott Deboy wrote:
I'd like to define a conversion pattern that would take:
org.apache.log4j.package1.package2.package3.classname
and output
package1.package2.package3.classname
Using some pattern like %p{3}
Basically stripping off the leading 3
On Feb 20, 2010, at 11:16 AM, Ralph Goers wrote:
I'd prefer a Message instead of an Object. The primary difference is that the
Message is an interface that looks like:
/**
* An interface for various Message implementations that can be logged.
*/
public interface Message extends
Author tags
---
Key: LOG4J2-30
URL: https://issues.apache.org/jira/browse/LOG4J2-30
Project: Log4j 2
Issue Type: Wish
Reporter: Curt Arnold
Priority: Minor
Logging this as a bug so that it eventually gets
at 3:39 PM, Curt Arnold carn...@apache.org wrote:
The scuttled 1.2.16 RC1 updated the staging site
(http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html).
I would not anticipate any structural changes, but we have a short window
where we could make some content changes
On Feb 19, 2010, at 5:42 PM, Christian Grobmeier wrote:
However - we (all who are interested in continuing log4j) need to
discuss other options. Using SLF4J as native interface or not might be
the next discussion. Looking at the current code we currently have is
the next one.
Before
The scuttled 1.2.16 RC1 updated the staging site
(http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html).
I would not anticipate any structural changes, but we have a short window
where we could make some content changes, such as removing the obsolete
benchmark for JDK
I believe this is a Ant issue and I've posted to d...@ant.apache.org.
For those who are not aware, Gump performs a clean build from source of the
head of several hundred projects several times a day to identify integration
issues as close to the point of introduction.
people.apache.org has been unresponsive for 6 or so hours now. I have not seen
any explanation on infrastruct...@apache or estimate of when it will be
accessible. Unfortunate timing. Will monitor the situation and cut log4j
1.2.16 RC1 at first opportunity.
I reverted the prudent mode patch
On Feb 13, 2010, at 3:58 PM, Ceki Gülcü wrote:
Isn't the write method in PrudentWriter (see [1]) a copy-and-paste of code
safeWrite() method in logback's FileAppender (see [2])?
[1]
On Feb 12, 2010, at 8:29 AM, bugzi...@apache.org wrote:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48704
--- Comment #7 from Ceki Gulcu c...@apache.org 2010-02-12 14:29:36 UTC ---
(In reply to comment #6)
I have not reviewed the logback implementation, but there is nothing that
On Dec 11, 2009, at 3:50 AM, Christian Grobmeier wrote:
Hi all,
I looked at the svn of Log4J and saw that there is no activity on the
2.0 branch for 17 months.
...
Since there is less activity at all, I would like to know about your
thoughts on the future development. I saw no posts at
On Oct 12, 2009, at 12:43 AM, Scott Deboy wrote:
- review 45753, 44932 for inclusion
- you commented that 43736 is a blocker for receivers release, so we
should review that as well
As for Chainsaw, 38884 and 29735 should be fixed prior to release
Scott
I was planning on reviewing 45753
FYI: I'm hoping to be able to cut a release candidate for 1.2.16
tomorrow. I've put a tentative release date of October 21th into the
changes log. My intent is to use the intervening time to prepare some
of the companions, log4j-extras, at minimum for a simultaneous release.
I'm
On Oct 9, 2009, at 8:18 AM, Jess Holle wrote:
Curt Arnold wrote:
2. org.apache.log4j.RollingFileAppender and
org.apache.log4j.DailyRollingFileAppender have a disproportionate
number of bugs. The extras companion has the log4j 1.3 rework
which still is subject to the multiple instance
EnhancedPatternLayout is another possibility for promotion from the
extras companion.
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
I should have some time this weekend to prepare a release candidate.
I've been going through the bug database trying to knock off some low-
hanging fruit.
Got a couple of questions I'd like feedback on.
1. The recent thread on parameterized logging briefly touched on LogSF
and LogMF in
1 - 100 of 637 matches
Mail list logo
