Currently, when using vibe-core as dependency and a different logging bridge is used, exclusions are needed. A fix is needed where vibe-core only uses a logging api interface.
Needed code when using as library that uses different logging bridge:
Error thrown by molgenis-app-vibe if exclusions are not present:
[INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-banned-dependencies) @ molgenis-app-vibe ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.slf4j:jcl-over-slf4j:jar:1.7.25
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
Currently, when using vibe-core as dependency and a different logging bridge is used, exclusions are needed. A fix is needed where
vibe-core
only uses a logging api interface.Needed code when using as library that uses different logging bridge:
Vibe-core maven dependency tree (stripped to relevant parts only):
Error thrown by
molgenis-app-vibe
if exclusions are not present: