Re: [VOTE] Release log4j 1.2.17 RC3

2012-05-08 Thread Curt Arnold
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

Re: log4j on Personal Basis Profile (was Re: [ANN] Deleting receivers and components 'companions')

2011-10-19 Thread Curt Arnold
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

log4j on Personal Basis Profile (was Re: [ANN] Deleting receivers and components 'companions')

2011-10-18 Thread 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

Re: [ANN] Deleting receivers and components 'companions'

2011-10-18 Thread Curt Arnold
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

Re: [ANN] Deleting receivers and components 'companions'

2011-10-11 Thread Curt Arnold
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

Re: [GUMP@vmgump]: Project logging-log4j-receivers (in module logging-log4j-receivers) failed

2011-10-11 Thread Curt Arnold
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

Re: [ANN] Deleting receivers and components 'companions'

2011-10-09 Thread Curt Arnold
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

Re: [ANN] Deleting receivers and components 'companions'

2011-10-06 Thread Curt Arnold
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

Re: log4j2 parameterized msg with throwable

2011-09-22 Thread Curt Arnold
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

Re: Companions - Chainsaw?

2011-09-02 Thread Curt Arnold
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:

Re: Companions - Chainsaw?

2011-09-01 Thread Curt Arnold
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

Re: [ANNOUNCEMENT} New comm...@logging.apache.org mailing list

2011-08-29 Thread Curt Arnold
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

Combine Component and Receivers into extras or Chainsaw (was Re: Missing commit messages for rev 1158186 1159577, 1159583_

2011-08-28 Thread Curt Arnold
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

[ANNOUNCEMENT} New comm...@logging.apache.org mailing list

2011-08-25 Thread Curt Arnold
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

Re: Missing commit messages for rev 1158186 1159577, 1159583

2011-08-25 Thread Curt Arnold
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

Re: Missing commit messages for rev 1158186 1159577, 1159583

2011-08-25 Thread Curt Arnold
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

Re: Removing the ant junit testing

2011-08-24 Thread Curt Arnold
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

Missing commit messages for rev 1158186 1159577, 1159583

2011-08-24 Thread Curt Arnold
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

Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml

2011-08-18 Thread Curt Arnold
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

Re: [companions] Which ones for chainsaw?

2011-08-16 Thread Curt Arnold
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

Personal note, month old concurrency threads and project annual meeting

2011-05-15 Thread Curt Arnold
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

Re: Contributing

2011-04-28 Thread Curt Arnold
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

Re: Avoiding the unnecessary message build cost

2011-04-05 Thread Curt Arnold
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

Re: Is it me or FilterBasedTriggeringPolicy has a bug!

2011-04-01 Thread Curt Arnold
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

Re: [VOTE RESULT] Apache extras companion for log4j, version 1.1

2011-03-07 Thread Curt Arnold
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

Re: svn commit: r1067833 [2/2] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j2-api/src/main/java/org/apache/logging/log4j/ log4j2-api/src/main/java/org/apache/logging/log4j/spi/

2011-02-06 Thread Curt Arnold
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

Re: ConversionPattern per Priority (ConsoleAppender)

2011-01-10 Thread Curt Arnold
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

Re: [GUMP@vmgump]: Project log4j2 (in module logging-log4j-2) failed

2011-01-09 Thread Curt Arnold
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

Re: Race condition in AsyncAppender

2010-12-12 Thread Curt Arnold
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

Re: JDBCAppender

2010-12-12 Thread Curt Arnold
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

Waiting for extras 1.1 to hit the maven repo

2010-12-09 Thread Curt Arnold
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

Re: [VOTE RESULT] Apache extras companion for log4j, version 1.1

2010-11-21 Thread Curt Arnold
/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

Re: other releases?

2010-11-19 Thread Curt Arnold
I've been trying to address the new project branding requirements at the same. Otherwise, we'd be needed to do a refresh of at least the web site in a few months. Stumbled through with extras looking for a path, but should be able to apply it to the other companions pretty quickly. You could

[VOTE RESULT] Apache extras companion for log4j, version 1.1

2010-11-19 Thread Curt Arnold
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

Re: [VOTE] Apache extras companion for log4j, version 1.1

2010-11-15 Thread Curt Arnold
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

Re: [VOTE] Apache extras companion for log4j, version 1.1

2010-11-14 Thread Curt Arnold
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

[VOTE] Apache extras companion for log4j, version 1.1

2010-11-13 Thread Curt Arnold
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

[jira] Created: (LOG4J2-45) Update site content for Apache Project Branding Requirements

2010-10-31 Thread Curt Arnold (JIRA)
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

Apache Project Branding requirements

2010-10-31 Thread Curt Arnold
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.

Re: Snowballs chance of getting Companion + Chainsaw releases out the door in time for ApacheCon?

2010-10-28 Thread Curt Arnold
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

Newest development: Isabella Claire Arnold

2010-09-17 Thread Curt Arnold
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:

Re: Time for a companions release

2010-09-04 Thread Curt Arnold
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

[jira] Commented: (LOG4J2-41) Extensible Log Level

2010-07-29 Thread Curt Arnold (JIRA)
[ 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

Re: [GUMP@vmgump]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

2010-07-06 Thread Curt Arnold
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,

Re: Chainsaw build error

2010-07-02 Thread Curt Arnold
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

Re: extras 1.1, component, receivers companions due for release

2010-06-19 Thread Curt Arnold
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

Re: extras 1.1, component, receivers companions due for release

2010-06-08 Thread Curt Arnold
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

extras 1.1, component, receivers companions due for release

2010-06-07 Thread Curt Arnold
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

Welcome Ralph Goers to the Logging Services PMC

2010-06-06 Thread Curt Arnold
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

Re: [g...@vmgump]: Project log4j2 (in module logging-log4j-2) failed

2010-06-06 Thread Curt Arnold
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

Re: [g...@vmgump]: Project log4j2 (in module logging-log4j-2) failed

2010-06-05 Thread Curt Arnold
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

[jira] Created: (LOG4J2-42) Improving log4j so it can easily be used with servlet logging

2010-06-01 Thread Curt Arnold (JIRA)
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

[jira] Commented: (LOG4J2-41) Extensible Log Level

2010-06-01 Thread Curt Arnold (JIRA)
[ 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

Re: svn commit: r949590 - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: log4j2-api/src/main/java/org/apache/logging/log4j/ log4j2-core/ log4j2-core/src/main/java/org/apache/logging/log4j/

2010-05-31 Thread Curt Arnold
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:

Re: Improving log4j so it can easily be used with servlet logging

2010-05-31 Thread Curt Arnold
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

Re: Improving log4j so it can easily be used with servlet logging

2010-05-31 Thread Curt Arnold
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

Re: Improving log4j so it can easily be used with servlet logging

2010-05-30 Thread 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 story). Currently that cannot be done,

[jira] Commented: (LOG4J2-10) log4j 2.0 should work well with OSGi and Apache Felix

2010-05-29 Thread Curt Arnold (JIRA)
[ 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

[jira] Created: (LOG4J2-37) Support getLogger(Object)

2010-05-29 Thread Curt Arnold (JIRA)
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

log4j2 sandbox

2010-05-29 Thread Curt Arnold
Moved some stuff around in the log4j2 sandbox at http://svn.apache.org/repos/asf/logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL. I fixed the test failures in the 2007 and 2008 vintage code. The were test utility problems that had previously affected log4j 1.2 but were not addressed in this

Re: svn commit: r948664 - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers/log4j2-core/src/main/java/org/apache/logging/log4j/core: ./ appender/ filter/

2010-05-27 Thread Curt Arnold
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

Re: svn commit: r948664 - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers/log4j2-core/src/main/java/org/apache/logging/log4j/core: ./ appender/ filter/

2010-05-27 Thread Curt Arnold
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

Re: log4j 2.0 code review process

2010-05-24 Thread Curt Arnold
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

[jira] Created: (LOG4J2-36) Appender interface should be refactored

2010-05-24 Thread Curt Arnold (JIRA)
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

[jira] Commented: (LOG4J2-36) Appender interface should be refactored

2010-05-24 Thread Curt Arnold (JIRA)
[ 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

Re: A new thread for log4j 2.0 discussion (Was Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12

2010-05-23 Thread Curt Arnold
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

log4j 2.0 code review process

2010-05-23 Thread Curt Arnold
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

Re: A new thread for log4j 2.0 discussion (Was Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12

2010-05-22 Thread Curt Arnold
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

Re: A new thread for log4j 2.0 discussion (Was Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12

2010-05-22 Thread Curt Arnold
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.

A new thread for log4j 2.0 discussion (Was Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api

2010-05-21 Thread Curt Arnold
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

Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api/src/main/java/ log4j12-api/src/main/java

2010-05-17 Thread Curt Arnold
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

Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api/src/main/java/ log4j12-api/src/main/java

2010-05-17 Thread Curt Arnold
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

Re: companions release

2010-05-16 Thread Curt Arnold
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

Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api/src/main/java/ log4j12-api/src/main/java/o

2010-05-14 Thread Curt Arnold
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

Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api/src/main/java/ log4j12-api/src/main/java/o

2010-05-14 Thread Curt Arnold
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

Re: svn commit: r943816 [1/9] - in /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers: ./ log4j12-api/ log4j12-api/src/ log4j12-api/src/main/ log4j12-api/src/main/java/ log4j12-api/src/main/java/o

2010-05-13 Thread Curt Arnold
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

Re: companions release

2010-05-04 Thread Curt Arnold
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 RESULT] Replacement log4j-1.2.16-javadoc.jar

2010-04-12 Thread Curt Arnold
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

[jira] Created: (LOG4J2-34) log4j 2 should be modular

2010-04-08 Thread Curt Arnold (JIRA)
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

Re: Modular Build

2010-04-08 Thread Curt Arnold
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 maintenance release though. You could never say with certainty that

[VOTE] Replacement log4j-1.2.16-javadoc.jar

2010-04-08 Thread Curt Arnold
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.

Re: [VOTE RESULT] log4j 1.2.16 release

2010-04-07 Thread Curt Arnold
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

Re: [VOTE RESULT] log4j 1.2.16 release

2010-04-07 Thread Curt Arnold
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

[VOTE RESULT] log4j 1.2.16 release

2010-04-06 Thread Curt Arnold
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

Re: [VOTE RESULT] log4j 1.2.16 release

2010-04-06 Thread Curt Arnold
#distribute-other-artifacts. I have removed just those files from http://people.apache.org/builds/logging/repo and will proceed to sync the other artifacts. On Apr 6, 2010, at 8:39 PM, Curt Arnold wrote: A belated +1 from me. Vote was open for 6 days, +1 votes from Scott Deboy, Christian

[VOTE] log4j 1.2.16 release

2010-03-30 Thread Curt Arnold
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:

log4j 1.2.16 RC1 available (but will be scuttled)

2010-03-28 Thread Curt Arnold
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:

Calling all JDK's

2010-03-27 Thread Curt Arnold
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

Re: NameAbbreviator

2010-03-27 Thread Curt Arnold
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

Re: Future development of Log4J?

2010-02-22 Thread Curt Arnold
On Feb 22, 2010, at 2:22 AM, Ralph Goers wrote: Well, I've finally begun doing some coding this weekend although I haven't gotten awfully far. I am definitely going to be using the Message interface. There were some lengthy discussions on the Logback list about this topic and the problems

Re: Future development of Log4J?

2010-02-22 Thread Curt Arnold
On Feb 22, 2010, at 7:45 AM, Curt Arnold wrote: Please start a directory off http://svn.apache.org/repos/asf/logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL for this work. We want to avoid having a whole bunch of code hit the SVN repo in a finished state. Please describe your approach

Re: Future development of Log4J?

2010-02-21 Thread Curt Arnold
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

[jira] Created: (LOG4J2-30) Author tags

2010-02-20 Thread Curt Arnold (JIRA)
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

Re: Website/docs comments

2010-02-20 Thread Curt Arnold
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

Re: Future development of Log4J?

2010-02-19 Thread Curt Arnold
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

Website/docs comments

2010-02-18 Thread Curt Arnold
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

Re: [GUMP@vmgump]: Project logging-log4j-12 (in module logging-log4j-12) failed

2010-02-17 Thread Curt Arnold
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.

log4j 1.2.16 RC1 when people.apache.org comes back up

2010-02-15 Thread Curt Arnold
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

Re: svn commit: r909868 - in /logging/log4j/trunk: src/changes/ src/main/java/org/apache/log4j/ src/main/java/org/apache/log4j/helpers/ tests/src/java/org/apache/log4j/ tests/witness/

2010-02-13 Thread Curt Arnold
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]

log4j governance (was Re: DO NOT REPLY [Bug 48704] Multiple Java Process...)

2010-02-12 Thread Curt Arnold
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

  1   2   3   4   5   6   7   >