SLF4J crashes jenkins
Hi,
I have a project that has several spring boot starter dependencies (v3.4.5) (they in turn have slf4j v1.7.36 as a dependency.)
Now i tried to make a jenkins pipeline (with a sonarqube server stage). But the fails because an method does not exist (which afaik was added in 2.0 of slf4j)
I'm aware of being able to exclude the slf4j v1.7.36 from the spring starter dependencies and explicitly naming the e.g. v2.0.17, but I'd like to know if that is safe (couldnt find any direct answer online)
And I'm not sure how extensive testing would need to be to ensure it's safe.
TL:DR: is it safe to exclude the slf4j v1.7.36 from spring boot starter dependencies and explicitly add v2.X.X to prevent from crashing the jenkins pipeline?
thanks in advance
I have a project that has several spring boot starter dependencies (v3.4.5) (they in turn have slf4j v1.7.36 as a dependency.)
Now i tried to make a jenkins pipeline (with a sonarqube server stage). But the fails because an method does not exist (which afaik was added in 2.0 of slf4j)
I'm aware of being able to exclude the slf4j v1.7.36 from the spring starter dependencies and explicitly naming the e.g. v2.0.17, but I'd like to know if that is safe (couldnt find any direct answer online)
And I'm not sure how extensive testing would need to be to ensure it's safe.
TL:DR: is it safe to exclude the slf4j v1.7.36 from spring boot starter dependencies and explicitly add v2.X.X to prevent from crashing the jenkins pipeline?
thanks in advance
