Re: using an alternative slf4j implementation

-Original Message- > From: Jacek Laskowski [mailto:ja...@japila.pl] > Sent: Monday, February 06, 2017 10:46 AM > To: Mendelson, Assaf > Cc: user > Subject: Re: using an alternative slf4j implementation > > Hi, > > Sounds like a quite involved development for me.

RE: using an alternative slf4j implementation

of forcing logback as the binding? -Original Message- From: Jacek Laskowski [mailto:ja...@japila.pl] Sent: Monday, February 06, 2017 10:46 AM To: Mendelson, Assaf Cc: user Subject: Re: using an alternative slf4j implementation Hi, Sounds like a quite involved development for me. I can't

Re: using an alternative slf4j implementation

to either send spark’s logs to log4j and my logs > to logback or send everything to logback. > > Assaf. > > > > From: Jacek Laskowski [mailto:ja...@japila.pl] > Sent: Monday, February 06, 2017 12:47 AM > To: Mendelson, Assaf > Cc: user > Subject: Re: using an

RE: using an alternative slf4j implementation

spark’s logs to log4j and my logs to logback or send everything to logback. Assaf. From: Jacek Laskowski [mailto:ja...@japila.pl] Sent: Monday, February 06, 2017 12:47 AM To: Mendelson, Assaf Cc: user Subject: Re: using an alternative slf4j implementation Hi, Shading conflicting dependencies

Re: using an alternative slf4j implementation

Hi, Shading conflicting dependencies? Jacek On 5 Feb 2017 3:56 p.m., "Mendelson, Assaf" wrote: > Hi, > > Spark seems to explicitly use log4j. > > This means that if I use an alternative backend for my application (e.g. > ch.qos.logback) I have a conflict. > > Sure I

using an alternative slf4j implementation

Hi, Spark seems to explicitly use log4j. This means that if I use an alternative backend for my application (e.g. ch.qos.logback) I have a conflict. Sure I can exclude logback but that means my application cannot use our internal tools. Is there a way to use logback as a backend logging while