Re: Migrating from Log4j 1

Not unless we implement it. I am not sure how it would be done. Somehow you would need a global exclude declaration - or possibly an exclude scope. Ralph > On Aug 12, 2016, at 6:33 PM, Remko Popma wrote: > > Are there any plans to support this in Maven? > > Sent from

Re: Migrating from Log4j 1

Are there any plans to support this in Maven? Sent from my iPhone > On 2016/08/13, at 9:59, Ralph Goers wrote: > > That’s the same thing SLF4J did - See http://slf4j.org/faq.html#excludingJCL. > Unfortunately, Maven doesn’t directly support it so you have to use

Re: Migrating from Log4j 1

That’s the same thing SLF4J did - See http://slf4j.org/faq.html#excludingJCL . Unfortunately, Maven doesn’t directly support it so you have to use one of these hacks. Ralph > On Aug 12, 2016, at 5:35 PM, Matt Sicker wrote: > > I

Re: Migrating from Log4j 1

I found this, looks promising: https://stackoverflow.com/a/4717025 On 12 August 2016 at 19:15, Remko Popma wrote: > In Maven, is there a global way to exclude a dependency? Perhaps we just > need to show people how to do this? > > Sent from my iPhone > > On 2016/08/13, at

Re: Migrating from Log4j 1

In Maven, is there a global way to exclude a dependency? Perhaps we just need to show people how to do this? Sent from my iPhone > On 2016/08/13, at 8:54, Matt Sicker wrote: > > However, as to #3, it looks like we may need to extend this upgrade epic to > non-Apache

Re: Migrating from Log4j 1

However, as to #3, it looks like we may need to extend this upgrade epic to non-Apache projects if possible to try and fix up the dependencies. Or wouldn't it be a neat feature for Maven to just transitively ban a dependency and provide a replacement? Perhaps this is more of a build tool problem

Re: Migrating from Log4j 1

It may sound somewhat smug, but OSGi doesn't really have the dependency hell problems addressed there. It has other annoyances, but you can run multiple versions of the same library in the same JVM without them even knowing about each other for instance. Plus, OSGi users have a full logging

Re: Migrating from Log4j 1

Just read this thread: https://issues.apache.org/jira/browse/SPARK-6305 Concerns: * User-supplied logging configurations would break * Spark code to suppress some overly verbose logging in dependencies (which ignore config?) -not sure about impact * POM changes to exclude log4j 1.2 - Spark

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419634#comment-15419634 ] Matt Sicker commented on LOG4J2-667: I was imagining it would be part of PatternLayout. > Add

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419633#comment-15419633 ] Matt Sicker commented on LOG4J2-667: Yeah, I think so. > Add customization for JSON Layout keys and

Re: Migrating from Log4j 1

Yeah, really, what's the alternative? And I do think that completing that Log4j1ConfigurationFactory would be a great way to get people to migrate if they don't even need to update configs. Though I'd hate to come across one of those configs in the wild because it's not nearly as well documented

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419616#comment-15419616 ] Gary Gregory commented on LOG4J2-1512: -- Check, then "includeStacktrace" is OK. > Option to exclude

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419583#comment-15419583 ] Ralph Goers commented on LOG4J2-1512: - Log4j 1 and Logback both always swallowed exceptions in

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419505#comment-15419505 ] Gary Gregory commented on LOG4J2-1512: -- Before I dig in: We have an inconsistency here. We

Re: Migrating from Log4j 1

Dropping Log4j 1 and doing what instead? Stop logging altogether? Logback’s configuration isn’t compatible either. Ralph > On Aug 12, 2016, at 9:52 AM, Mikael Ståldal wrote: > > There seem to be quite some frustration in some other Apache projects about >

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419443#comment-15419443 ] Mikael Ståldal commented on LOG4J2-1512: Implemented for JsonLayout, XmlLayout and YamlLayout in

[jira] [Assigned] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1512: -- Assignee: Mikael Ståldal > Option to exclude stack trace from some layouts >

[jira] [Updated] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1512: --- Fix Version/s: 2.7 > Option to exclude stack trace from some layouts >

Re: Migrating from Log4j 1

I'd be happy to help of course since I started the adapter. Gary On Fri, Aug 12, 2016 at 10:06 AM, Gary Gregory wrote: > Please consider expanding what I started here org.apache.log4j.config. > Log4j1ConfigurationFactory > > Gary > > On Fri, Aug 12, 2016 at 9:52 AM,

Re: Migrating from Log4j 1

Please consider expanding what I started here org.apache.log4j.config.Log4j1ConfigurationFactory Gary On Fri, Aug 12, 2016 at 9:52 AM, Mikael Ståldal wrote: > There seem to be quite some frustration in some other Apache projects > about migrating from Log4j 1.

Migrating from Log4j 1

There seem to be quite some frustration in some other Apache projects about migrating from Log4j 1. Especially around configration. Some seem to consider dropping Log4j completely instead of going for Log4j 2. I have taken on Spark, Hadoop and Zookeeper; see links to their Jira issues from

[jira] [Assigned] (LOG4J2-1514) Help Apache Zookeeper project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1514: -- Assignee: Mikael Ståldal > Help Apache Zookeeper project to upgrade from Log4j 1.x to

[jira] [Created] (LOG4J2-1514) Help Apache Zookeeper project to upgrade from Log4j 1.x to 2.x

Mikael Ståldal created LOG4J2-1514: -- Summary: Help Apache Zookeeper project to upgrade from Log4j 1.x to 2.x Key: LOG4J2-1514 URL: https://issues.apache.org/jira/browse/LOG4J2-1514 Project: Log4j 2

[jira] [Assigned] (LOG4J2-1503) Help Apache Hadoop project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1503: -- Assignee: Mikael Ståldal > Help Apache Hadoop project to upgrade from Log4j 1.x to

[jira] [Created] (LOG4J2-1513) Configuration properties file is locked

Jean-Noel Charpin created LOG4J2-1513: - Summary: Configuration properties file is locked Key: LOG4J2-1513 URL: https://issues.apache.org/jira/browse/LOG4J2-1513 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418643#comment-15418643 ] Mikael Ståldal commented on LOG4J2-667: --- That being said, it would make sense to add an option to

[jira] [Commented] (LOG4J2-1512) Option to exclude stack trace from some layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418639#comment-15418639 ] Mikael Ståldal commented on LOG4J2-1512: This would improve the customability of JsonLayout a

[jira] [Created] (LOG4J2-1512) Option to exclude stack trace from some layouts

Mikael Ståldal created LOG4J2-1512: -- Summary: Option to exclude stack trace from some layouts Key: LOG4J2-1512 URL: https://issues.apache.org/jira/browse/LOG4J2-1512 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1284) Make default MessageFactory configurable

[ https://issues.apache.org/jira/browse/LOG4J2-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418627#comment-15418627 ] Fabien Baligand commented on LOG4J2-1284: - Thanks for the info. I suppose you reopen the issue to

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418625#comment-15418625 ] Mikael Ståldal commented on LOG4J2-667: --- Would it make sense to add yaml and csv here as well? >

[jira] [Comment Edited] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418616#comment-15418616 ] Mikael Ståldal edited comment on LOG4J2-667 at 8/12/16 10:14 AM: - I would

[jira] [Comment Edited] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418616#comment-15418616 ] Mikael Ståldal edited comment on LOG4J2-667 at 8/12/16 10:13 AM: - I would

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418619#comment-15418619 ] Mikael Ståldal commented on LOG4J2-667: --- Should this be for JsonLayout or PatternLayout? I think we

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418616#comment-15418616 ] Mikael Ståldal commented on LOG4J2-667: --- I would say that the purpose of the JsonLayout in Log4j is

[jira] [Commented] (LOG4J2-1510) why MutableLogEvent don't keep original log object or even the ReusableObjectMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418388#comment-15418388 ] Remko Popma commented on LOG4J2-1510: - Yes, this is on purpose. With asynchronous logging, we need