Hi,
In order to avoid unnecessary dependencies, we need to exclude the SLF4J implementation forced by the upstream pom. This is a bug in the upstream raml.org project:
https://github.com/raml-org/raml-java-parser/pull/65
If we exclude the binding, the binding and the associated log4j dependency should not be imported.
Coverage remained the same at 100.0% when pulling 3e454f80c25352f1f789d1c928dc1a520abfe3c7 on bdellegrazie:exclude-log4j-impl into 9b2a16122924692eff753e48f0ed49e835a8b501 on CJSCommonPlatform:master.
Coverage remained the same at 100.0% when pulling a95405291bb849578345205164e88f9b568f2edf on bdellegrazie:exclude-log4j-impl into 9b2a16122924692eff753e48f0ed49e835a8b501 on CJSCommonPlatform:master.
Hi, In order to avoid unnecessary dependencies, we need to exclude the SLF4J implementation forced by the upstream pom. This is a bug in the upstream raml.org project: https://github.com/raml-org/raml-java-parser/pull/65
If we exclude the binding, the binding and the associated log4j dependency should not be imported.