I've cut a release candidate for apache-log4j-component. Jars are
available in the staging Maven repository at http://
people.apache.org/builds/logging/repo, distributions are at http://
people.apache.org/builds/logging/log4j/companions/component/1.0 and
documentation is online at
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 complete.
Also, I'm not sure of the state of our
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
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
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
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
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
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
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
Author: carnold
Date: Thu Jun 21 13:54:11 2007
New Revision: 549608
URL: http://svn.apache.org/viewvc?view=revrev=549608
Log:
Bug 37930: Remove C artifacts from log4j.jar
Modified:
logging/log4j/branches/v1_2-branch/src/ntdll/build.xml
Modified:
Author: carnold
Date: Thu Jun 21 13:54:51 2007
New Revision: 549609
URL: http://svn.apache.org/viewvc?view=revrev=549609
Log:
Bug 37930: Update build date (speculative)
Modified:
logging/log4j/branches/v1_2-branch/src/changes/changes.xml
Modified:
Author: carnold
Date: Thu Jun 21 13:55:23 2007
New Revision: 549610
URL: http://svn.apache.org/viewvc?view=revrev=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:
Author: carnold
Date: Thu Jun 21 13:56:12 2007
New Revision: 549611
URL: http://svn.apache.org/viewvc?view=revrev=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:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=42664.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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.
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
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
Author: carnold
Date: Thu Jun 21 15:12:45 2007
New Revision: 549629
URL: http://svn.apache.org/viewvc?view=revrev=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:
Author: carnold
Date: Thu Jun 21 15:23:21 2007
New Revision: 549634
URL: http://svn.apache.org/viewvc?view=revrev=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:
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
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:
21 matches
Mail list logo
