Re: [Patch review please] Further work for Receivers backport to 1.2

On Apr 18, 2007, at 10:31 PM, Paul Smith wrote: Maybe you could fake out the getLogger() calls like private static final class LogLogger { public void debug(final String msg) { LogLog.debug(msg); } public void warn(final String msg) {

Re: Chainsaw & log4j 1.2 status

On Apr 18, 2007, at 11:05 PM, Paul Smith wrote: This is because the LoggerRepository is not of type LoggerRepositoryEx. Chainsaw makes extensive use of the PluginRegistry, and right now we have no central place where it can access a PluginRegistry. What I'll do is create a PluginRegis

Re: Chainsaw & log4j 1.2 status

This is because the LoggerRepository is not of type LoggerRepositoryEx. Chainsaw makes extensive use of the PluginRegistry, and right now we have no central place where it can access a PluginRegistry. What I'll do is create a PluginRegistry somewhere higher up, and hand this down to th

Chainsaw & log4j 1.2 status

First time trying to startup Chainsaw with the new dependency: Exception in thread "main" java.lang.NullPointerException at org.apache.log4j.chainsaw.receivers.ReceiversPanel. (ReceiversPanel.java:395) at org.apache.log4j.chainsaw.LogUI.setupReceiverPanel(LogUI.java:493) at org

Re: [Patch review please] Further work for Receivers backport to 1.2

Maybe you could fake out the getLogger() calls like private static final class LogLogger { public void debug(final String msg) { LogLog.debug(msg); } public void warn(final String msg) { LogLog.warn(msg); }

Re: [Patch review please] Further work for Receivers backport to 1.2

On 18/04/2007, at 2:46 PM, Scott Deboy wrote: In DBAppender: insertStatement.setLong(0, 0); should be insertStatement.setLong(1, 0); done, well spotted. Also, in CustomSQLDBReceiver: Should LoggingEvent event = new LoggingEvent(null, eventLogger, timeStamp, levelImpl, message, threadName,

svn commit: r530249 - in /logging/sandbox/log4j/receivers: ./ src/main/java/org/apache/log4j/db/ src/main/java/org/apache/log4j/net/

Author: psmith Date: Wed Apr 18 20:25:33 2007 New Revision: 530249 URL: http://svn.apache.org/viewvc?view=rev&rev=530249 Log: Final tidy up of addition of other receivers from log4j 1.3. Reviewed by: Curt and Scott Added: logging/sandbox/log4j/receivers/src/main/java/org/apache/log4j/db/

svn commit: r530138 - in /logging/sandbox/log4j/receivers/src/main/resources: ./ META-INF/ META-INF/LICENSE META-INF/NOTICE

Author: carnold Date: Wed Apr 18 12:39:39 2007 New Revision: 530138 URL: http://svn.apache.org/viewvc?view=rev&rev=530138 Log: Bug 42102: Add LICENSE and NOTICE to jar's META-INF Added: logging/sandbox/log4j/receivers/src/main/resources/ logging/sandbox/log4j/receivers/src/main/resources/

svn commit: r530137 - in /logging/sandbox/log4j/expression-filter/src/main/resources: ./ META-INF/ META-INF/LICENSE META-INF/NOTICE

Author: carnold Date: Wed Apr 18 12:38:11 2007 New Revision: 530137 URL: http://svn.apache.org/viewvc?view=rev&rev=530137 Log: Bug 42099: Add NOTICE and LICENSE to jar's META-INF Added: logging/sandbox/log4j/expression-filter/src/main/resources/ logging/sandbox/log4j/expression-filter/src

svn commit: r530135 - in /logging/sandbox/log4j/component/src/main/resources: ./ META-INF/ META-INF/LICENSE META-INF/NOTICE

Author: carnold Date: Wed Apr 18 12:36:23 2007 New Revision: 530135 URL: http://svn.apache.org/viewvc?view=rev&rev=530135 Log: Bug 42094: Add NOTICE and LICENSE to jar Added: logging/sandbox/log4j/component/src/main/resources/ logging/sandbox/log4j/component/src/main/resources/META-INF/

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) 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-tests has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) 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-tests has an issue affecting its community integration. This issue

DO NOT REPLY [Bug 42151] - StackOverFlow in flush() method of LoggingOutputStream

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

AW: maven and jms

ooops, i'm sorry, as far as i can see, jms is not in that repository :-/ but others like javax.activation, javax.mail, javax.servlet etc. are in there. at least. > -Ursprüngliche Nachricht- > Von: Wyss Patrick [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 18. April 2007 09:13 > An: Log4

AW: maven and jms

alternatively you could add suns maven repository: https://maven-repository.dev.java.net/nonav/repository to the pom or settings: java.net https://maven-repository.dev.java.net/nonav/repository legacy however i do not see this often in OS projects, so i have no clue if this is considered

AW: "Compelling Reasons to adopt log4j2"

> > * Ease of migration/Drop in replacement for log4j 1.2 - If we do > > not meet this fundamental goal, I seriously doubt we'll ever gain > > traction. We should be free from the log4j1.2 design, but we > > should begin early to ensure that the core design can be easily > > shimmed with a