[
https://issues.apache.org/jira/browse/RATIS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated RATIS-827:
------------------------------
Attachment: RATIS-827.001.patch
> Ratis example is leaking to the ratis-tools classpath
> -----------------------------------------------------
>
> Key: RATIS-827
> URL: https://issues.apache.org/jira/browse/RATIS-827
> Project: Ratis
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Critical
> Attachments: RATIS-827.001.patch
>
>
> ratis-tools depends on ratis-example project which means that all the
> projects using ratis-tools can get unexpected dependencies from the example
> project:
> For example I see the following ozone.
> {code}
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/opt/hadoop/share/ozone/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/opt/hadoop/share/ozone/lib/ratis-examples-0.6.0-a320ae0-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> {code}
> I propose to move the example dependent tools implementation to the example
> project and make the example project depends on the tools instead of the
> opposite direction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
