RE: JUL appender

Paul, 'jul' it is. Should I check in under the v1_2branch? By the way, where can I find info on the bridge project you mentioned? Thanks. Sagi Mann -- *From:* Paul Smith [mailto:[EMAIL PROTECTED] *Sent:* Fri 6/22/2007 01:04 *To:* Log4J Developers List *Subject:* Re:

CLIRR report for log4j 1.2.15

After further review, it looks like the JDiff plugin for Maven 2 isn't available, there are no jars for it in the master Maven repo. A CLIRR plugin is available and is functional, but throws a NPE when evaluating log4j when it runs into an interface that it can't load (typically javax.jms.

svn commit: r549634 - /logging/log4j/branches/v1_2-branch/build.xml

Author: carnold Date: Thu Jun 21 15:23:21 2007 New Revision: 549634 URL: http://svn.apache.org/viewvc?view=rev&rev=549634 Log: Bug 37930: Update clirr task for Maven build Modified: logging/log4j/branches/v1_2-branch/build.xml Modified: logging/log4j/branches/v1_2-branch/build.xml URL: http

svn commit: r549629 - in /logging/log4j/branches/v1_2-branch: build.xml pom.xml

Author: carnold Date: Thu Jun 21 15:12:45 2007 New Revision: 549629 URL: http://svn.apache.org/viewvc?view=rev&rev=549629 Log: Bug 37930: Update clirr task for Maven build Modified: logging/log4j/branches/v1_2-branch/build.xml logging/log4j/branches/v1_2-branch/pom.xml Modified: logging/

Re: JUL appender

I think 'org.apache.log4j.jul' might be a good choice for packaging. That's what I've used for log4j related code in the jul-log4j-bridge project. Any non-log4j class (or more formally, all java.util.logging) code could go in 'org.apache.logging.jul'. This way there is a clean seperation

Re: svn commit: r549610 - /logging/log4j/branches/v1_2-branch/BUILD-INFO.txt

Just an additional note on maven deployment that I've learned the hard way, perhaps you might want to consider adding this as a note. Maven or the Wagon deployment plugin appears to assume the local username is the destination username, _even_ if you specify a username property in the setti

Re: JUL appender

Got it working. Thanks, Paul. The testcase is now attached in issue 42664: http://issues.apache.org/bugzilla/show_bug.cgi?id=42664 I'd appreciate if someone verifies this is the expected kind of test case. Currently, both appender and test classes are defined under the org.apache.log4j package. W

DO NOT REPLY [Bug 42664] - JUL Appender

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

svn commit: r549611 - /logging/log4j/branches/v1_2-branch/pom.xml

Author: carnold Date: Thu Jun 21 13:56:12 2007 New Revision: 549611 URL: http://svn.apache.org/viewvc?view=rev&rev=549611 Log: Bug 37930: Revert back to 1.2.15 snapshot and simplify release goals Modified: logging/log4j/branches/v1_2-branch/pom.xml Modified: logging/log4j/branches/v1_2-branc

svn commit: r549610 - /logging/log4j/branches/v1_2-branch/BUILD-INFO.txt

Author: carnold Date: Thu Jun 21 13:55:23 2007 New Revision: 549610 URL: http://svn.apache.org/viewvc?view=rev&rev=549610 Log: Bug 37930: Add Maven settings.xml info Modified: logging/log4j/branches/v1_2-branch/BUILD-INFO.txt Modified: logging/log4j/branches/v1_2-branch/BUILD-INFO.txt URL:

svn commit: r549609 - /logging/log4j/branches/v1_2-branch/src/changes/changes.xml

Author: carnold Date: Thu Jun 21 13:54:51 2007 New Revision: 549609 URL: http://svn.apache.org/viewvc?view=rev&rev=549609 Log: Bug 37930: Update build date (speculative) Modified: logging/log4j/branches/v1_2-branch/src/changes/changes.xml Modified: logging/log4j/branches/v1_2-branch/src/chan

svn commit: r549608 - /logging/log4j/branches/v1_2-branch/src/ntdll/build.xml

Author: carnold Date: Thu Jun 21 13:54:11 2007 New Revision: 549608 URL: http://svn.apache.org/viewvc?view=rev&rev=549608 Log: Bug 37930: Remove C artifacts from log4j.jar Modified: logging/log4j/branches/v1_2-branch/src/ntdll/build.xml Modified: logging/log4j/branches/v1_2-branch/src/ntdll/

Re: apache-log4j-component-1.0 rc2

On Jun 21, 2007, at 12:56 PM, Scott Deboy wrote: I'd like to finish implementing repository-wide property support - I think what would solve both issues is to have LoggingEvent.getProperties just return the repository properties, not the MDC properties. LoggingEvent.getMDC would continue to

RE: apache-log4j-component-1.0 rc2

I'd like to finish implementing repository-wide property support - I think what would solve both issues is to have LoggingEvent.getProperties just return the repository properties, not the MDC properties. LoggingEvent.getMDC would continue to return only MDC-defined properties. That's enough to me

Re: apache-log4j-component-1.0 rc2

On Jun 21, 2007, at 1:18 AM, Scott Deboy wrote: I'd still like us to consider finishing the property support included in LoggerRepositoryEx (mostly requiring new functionality being added to LoggingEvent). It would make finishing up the backporting of the appenders & receivers essentially

Re: JUL appender

On Jun 21, 2007, at 8:16 AM, Sagi Mann wrote: Still, same error. Any advice? Can I get SVN to produce more error detail? I use the cmdline: svn checkout http://svn.apache.org/repos/asf/logging/log4j/branches/ v1_2-branch/ Thanks, Sagi Mann Try https: instead of http:. Firewalls and c

[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-chainsaw has an issue affecting its community integration. This iss

[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-chainsaw has an issue affecting its community integration. This iss

RE: apache-log4j-component-1.0 rc2

We can write it so that the repository-set properties are either available via getMDC or not - I don't care either way, since I could use getProperties on loggingevent to retrieve the MDC + repo properties. slf4j has gained some traction out there - it seems as though our direction (providing a

RE: JUL appender

Still, same error. Any advice? Can I get SVN to produce more error detail? I use the cmdline: svn checkout http://svn.apache.org/repos/asf/logging/log4j/branches/v1_2-branch/ Thanks, Sagi Mann From: Paul Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 2

Re: apache-log4j-component-1.0 rc2

On 21/06/2007, at 4:18 PM, Scott Deboy wrote: I'd still like us to consider finishing the property support included in LoggerRepositoryEx (mostly requiring new functionality being added to LoggingEvent). It would make finishing up the backporting of the appenders & receivers essentially c