[slf4j-dev] [JIRA] (SLF4J-369) Make slf4j-ext usage of CAL10N as optional depedency

QOS.CH (JIRA) noreply-jira at qos.ch
Thu Feb 23 05:21:00 CET 2017

    [ https://jira.qos.ch/browse/SLF4J-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18207#comment-18207 ] 

Jeremy Landis commented on SLF4J-369:

Can you explain more?  Is this getting a stack trace such as class not found if you don't include it?  If so, then it's not optional.  I've never ran into any issue with this so I'd like to understand it a bit.  I've got slf4j & logback in 100+ applications so trying to grasp how this is an issue.  I have slf4j-ext in all those too.

> Make slf4j-ext usage of CAL10N as optional depedency
> ----------------------------------------------------
>                 Key: SLF4J-369
>                 URL: https://jira.qos.ch/browse/SLF4J-369
>             Project: SLF4J
>          Issue Type: Bug
>          Components: slf4j-ext
>            Reporter: Matej Spiller-Muys
>            Assignee: SLF4J developers list
>            Priority: Critical
>             Fix For: 1.7.24
> I came across this issue because there is bug in CAL10N code (filled separately) that is crashing the compiler. But the reason for this issue is different. Slf4j-ext contains different extensions. In my case we are not even using features from cal10n, but because of slf4j-ext it is now scanning and checking my code regardless (from 0.8). Make slf4j-ext usage of CAL10N as optional dependency.
> from manual:
> In order to use CAL10N in a project, all you need is to add cal10n-api-0.8.1.jar onto your project's class path.

This message was sent by Atlassian JIRA

More information about the slf4j-dev mailing list