search

Knotx / knotx

Knot.x is a highly-efficient and scalable integration framework designed to build backend APIs
https://knotx.io
Apache License 2.0
126 stars 26 forks source link

Logger issues after running bin/knotx resolve #460

Closed 2kodes closed 5 years ago

2kodes commented 5 years ago

Version Used knot.x 1.4.0

Bug description After adding vertx dependency to knotx-stack.json and running bin/knotx resolve, running bin/knotx run-knotx will start up knotx but no startup information will be logged to knotx.log. Also there is an error message about multiple SLF4J bindings

To Reproduce

  1. Add dependency below to knotx-stack.json

    { "groupId": "io.vertx", "artifactId": "vertx-zookeeper", "version": "${vertx.version}", "included": true }

  2. Run bin/knotx resolve

  3. After resolution ends run bin/knotx run-knotx

  4. Knotx starts up but startup information is not logged to knotx.log.

Expected behavior After resolving dependencies knot.x should run normally and log started verticles to log file

Screenshots image

pawel-przystarz commented 5 years ago

Zookeeper has his own dependency for slf4j, so that's why we get this warns about multiple slf4j bindings. So the simplest way is to add an exclusion to the dependency like that:

{ "groupId": "io.vertx", "artifactId": "vertx-zookeeper", "version": "${vertx.version}", "included": true, "exclusions": [ { "groupId": "org.slf4j", "artifactId": "slf4j-log4j12" } ] }

tomaszmichalak commented 5 years ago

@2kodes I think it should answer your question. Closing the issue.