But if you search in the code for apache.commons.logging you find quite a bit of classes that depend on it. For example ConceptReferenceTermEditor; there are many more.
So
Should I create an issue with fixed in release 2.2.0 that will replace all occurrences of the apache.commons.logging with slf4j AND eliminate the apache.commons dependency that seems to slip in somewhere by another dependency
One concern–thoughts on how this will affect modules that might be making the same mistake, and may be relying on the apache.commons dependency that manages to slip in somewhere? If it may break them, we’ll need to document the fix for module owners.
@teleivo after merging your pull request, i just noticed that our commons.logging comes from jcl-over-slf4j-1.6.0.jar
Is it the one mentioned in the above spring link?