[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod

JIRA noreply-jira@qos.ch

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

Lin Wang commented on SLF4J-328:

Never mind, my bad, I used to have the following line to exclude a transitive dependency on slf4j-api in my gradle file since slf4j-api was built into slf4j-android 1.6.1-RC1.

*configurations.all*.exclude module: 'slf4j-api'*

After removing that line, I can successfully compile slf4j-android:1.7.25 now, since slf4j-android:1.7.x doesn't include the slf4j-api directly anymore.


> Binding Ambiguity check skipped for Andriod
> -------------------------------------------
>                 Key: SLF4J-328
>                 URL: https://jira.qos.ch/browse/SLF4J-328
>             Project: SLF4J
>          Issue Type: Improvement
>          Components: Core API
>    Affects Versions: 1.7.x
>         Environment: Android
>            Reporter: Nitin Verma
>            Assignee: Ceki Gülcü
>            Priority: Critical
>             Fix For: 1.7.14
>         Attachments: FindStaticLoggerBinderPathsPerfTest.java
> https://github.com/nitinverma/slf4j/commit/4d67b578fdc1cf77a0689f2efb0424f6c8479963
> As Dex cant by design have duplicate class, there would never be a 'Binding Ambiguity'.
> 1. LoggerFactory.getLogger is mostly called via MainActivity. Which gives a black screen before the first activity loads.
> 2. This operation takes 200-600 Inclusive CPU Time as per DDMS.
> This fix get Incl CPU Time to sub 10

This message was sent by Atlassian JIRA
slf4j-dev mailing list
[hidden email]