Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: updating to slf4j 2.0.x is a breaking change

See original GitHub issue

Module

Core

Testcontainers version

1.17.4

Using the latest Testcontainers version?

Yes

Host OS

macOS

Host Arch

x86

Docker version

Client:
 Cloud integration: v1.0.22
 Version:           20.10.11
 API version:       1.41
 Go version:        go1.16.10
 Git commit:        dea9396
 Built:             Thu Nov 18 00:36:09 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.11
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.9
  Git commit:       847da18
  Built:            Thu Nov 18 00:35:39 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

What happened?

Slf4j 2.0 is not compatible with spring boot. It was upgraded in #5848 Upgrading any dependency to the next major version in the next minor release of Testcontainers is not a good idea.

Please revert it to the 1.7.36

Relevant log output

No response

Additional Information

No response

Issue Analytics

State:
Created a year ago
Reactions:3
Comments:7 (3 by maintainers)

Top GitHub Comments

3reactions

marcindabrowskicommented, Oct 4, 2022

Sorry for misleading you, WireMock has nothing to do with this. I don’t know why I mentioned it here. Everywhere I wrote WireMock I meant testcontainers. Probably I’m too tired.

0reactions

kiviewcommented, Oct 4, 2022

Closed by #5951.

@marcindabrowski No problem, thanks for creating the issue.