Skip to content

Exclude commons-logging dependency from Elasticsearch dependencies. #1993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

sothawo
Copy link
Collaborator

@sothawo sothawo commented Nov 13, 2021

Closes #1989

@sothawo sothawo merged commit 95401a5 into spring-projects:4.3.x Nov 13, 2021
sothawo added a commit that referenced this pull request Nov 13, 2021
Original Pull Request #1993
Closes #1989

(cherry picked from commit 95401a5)
sothawo added a commit that referenced this pull request Nov 13, 2021
Original Pull Request #1993
Closes #1989

(cherry picked from commit 95401a5)
(cherry picked from commit 15ca49a)
@sothawo sothawo linked an issue Nov 13, 2021 that may be closed by this pull request
@sothawo sothawo deleted the #1989-exclude-commons-logging-dependency branch November 13, 2021 17:19
npepinpe added a commit to camunda/camunda that referenced this pull request Jul 3, 2023
Spring displays a prominent warning when using different versions of
`commons-logging`. They use their own variant, `spring-jcl`, and
importing `commons-logging` conflicts with this.

We pull in `commons-logging` via the Opensearch and Elasticsearch
exporters respectively. I have not noticed any issues with logging when
removing, and followed the suggestion from Spring themselves, see:

spring-projects/spring-data-elasticsearch#1993
ghost pushed a commit to camunda/camunda that referenced this pull request Jul 4, 2023
13300: fix(dist): remove Spring Boot warning around commons-logging r=remcowesterhoud a=npepinpe

## Description

Spring displays a prominent warning when using different versions of `commons-logging`. They use their own variant, `spring-jcl`, and importing `commons-logging` conflicts with this.

We pull in `commons-logging` via the Opensearch and Elasticsearch exporters respectively. I have not noticed any issues with logging when removing, and followed the suggestion from Spring themselves, see:

spring-projects/spring-data-elasticsearch#1993

## Related issues

closes #13299



Co-authored-by: Nicolas Pepin-Perreault <[email protected]>
npepinpe added a commit to camunda/camunda that referenced this pull request Jul 17, 2023
Spring displays a prominent warning when using different versions of
`commons-logging`. They use their own variant, `spring-jcl`, and
importing `commons-logging` conflicts with this.

We pull in `commons-logging` via the Opensearch and Elasticsearch
exporters respectively. I have not noticed any issues with logging when
removing, and followed the suggestion from Spring themselves, see:

spring-projects/spring-data-elasticsearch#1993
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

commons-logging:commons-logging should not be a transitive dependency
1 participant