One complaint I keep seeing is that libraries coding to the Log4j2 API would 
somehow result in problems with dependency configuration. 

I have been fairly isolated from such kind of problems so I don't understand 
when this could happen and what might cause it. 

The only hint I got was a brief reply on twitter: 
"Problems I've had result in lots of slf4j exclusions in my maven deps. IIRC 
the biggest offender was Jersey, but I don't have access to the project 
anymore."

When/why would it be necessary to have lots of slf4j exclusions in the maven 
dependencies?

Is there something we can do (docs or otherwise) to help with this? (Not sure 
if/how the log4j-boot project would help with such issues, I never used Spring 
boot.)

Remko 

Sent from my iPhone

> On Jan 15, 2017, at 13:59, Matt Sicker <boa...@gmail.com> wrote:
> 
> I've been seeing your posts on /r/java which could help spark some 
> discussions. :)
> 
>> On 14 January 2017 at 22:57, Remko Popma <remko.po...@gmail.com> wrote:
>> Another one along similar lines: "10 Log4j2 API features not in SLF4J" 
>> http://stackoverflow.com/a/41635246/1446916
>> 
>> :-)
>> Remko
>> 
>> Sent from my iPhone
>> 
>>> On Jan 13, 2017, at 14:15, Matt Sicker <boa...@gmail.com> wrote:
>>> 
>>> Jira is down right now, but I have this RFC: 
>>> https://github.com/apache/logging-log4j-boot
>>> 
>>>> On 8 January 2017 at 02:16, Remko Popma <remko.po...@gmail.com> wrote:
>>>> Speaking of slf4j, I would like to evangelize that applications should 
>>>> code to the Log4j2 API as a best practice. See also 
>>>> http://stackoverflow.com/a/41500347/1446916
>>>> 
>>>> I'm thinking to do a blog post along these lines.
>>>> 
>>>> Thoughts? Maybe also something to emphasize on the site?
>>>> 
>>>> Sent from my iPhone
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Matt Sicker <boa...@gmail.com>
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com>

Reply via email to