[
https://jira.qos.ch/browse/SLF4J-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gülcü resolved SLF4J-369.
------------------------------
Resolution: Fixed
Fixed in https://github.com/qos-ch/slf4j/commit/379574b7445e7b0b1f
> 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: Ceki Gülcü
> 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
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
