[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 09:38:00 CET 2017
[ https://jira.qos.ch/browse/SLF4J-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18209#comment-18209 ]
Matej Spiller-Muys commented on SLF4J-369:
------------------------------------------
Separate issue was reported inside cal10n: CAL-48.
Problem is because cal10n (and slf4j-ext) is doing something in addition during compile process on EVERY project that has dependency on it. If everything goes well, you don't see any issue. And you don't get any error. Well perhaps just a bit longer compilation phases.
But due to CAL-48 bug you got busted jar and successful build!!!
If you want cal10n compiler phase in you project, well then you should include it in your application yourself (like documentation states). I want to have build process under full control and don't want logger library to be more that it is supposed to (like checking translation in MY project).
> 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
(v7.3.1#73012)
More information about the slf4j-dev
mailing list