Dependency management has unnecessary log4j exclusion for spring-cloud-spring-service-connector #18833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... spring-cloud-spring-service-connector.
The dependency on
log4j:log4j
appears to have been removed from spring-cloud-spring-service-connector in late 2014 as part of spring-cloud-connectors issue #96, in commit f2be5e94305446d4698636a9037bf44185f418ed (2014-11-24), which was included beginning with spring-cloud-connectorsv1.1.1.RELEASE
.I did a quick example app using spring-cloud-spring-service-connector
2.0.6.RELEASE
and do not seelog4j:log4j
....and now I see that Spring Cloud Connectors is
...so perhaps this is moot. Or perhaps it's worth removing six unneeded lines from this file.