flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Hogan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4782) log4j & slf4j-log4j are present in jar-with-dependencies artifacts
Date Wed, 14 Dec 2016 18:47:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749108#comment-15749108
] 

Greg Hogan commented on FLINK-4782:
-----------------------------------

flink-metrics-dropwizard-1.2-SNAPSHOT-jar-with-dependencies.jar
flink-metrics-ganglia-1.2-SNAPSHOT-jar-with-dependencies.jar
flink-metrics-graphite-1.2-SNAPSHOT-jar-with-dependencies.jar

Shouldn't log4j and slf4j-log4j12 be marked as scope provided in the parent pom?

> log4j & slf4j-log4j are present in jar-with-dependencies artifacts
> ------------------------------------------------------------------
>
>                 Key: FLINK-4782
>                 URL: https://issues.apache.org/jira/browse/FLINK-4782
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System, Metrics
>    Affects Versions: 1.1.2
>            Reporter: Maciej Prochniak
>            Priority: Minor
>
> This makes it more difficult to use dropwizard metrics with e.g. logback
> It's because they are declared in parent pom as compile scope dependencies. 
> I don't clearly understand why is it this way - I'd rather have them provided (as they
are still specified in dist) but maybe there are some good reasons for that?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message