We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When there is testcontainers dependency, there are 2 junit dependencies. The results in IDE are:
testcontainers
To avoid this, we should exclude junit:
<dependency> <groupId>org.testcontainers</groupId> <artifactId>postgresql</artifactId> <version>${testcontainers.version}</version> <exclusions> <exclusion> <groupId>junit</groupId> <artifactId>junit</artifactId> </exclusion> </exclusions> <scope>test</scope> </dependency>
The text was updated successfully, but these errors were encountered:
I stumbled upon this issue a few days ago, but it's not as simple as excluding the dependency. See testcontainers/testcontainers-java#970 There's still a runtime dependency required by testcontainers. A workaround is to recreate fake junit4 rules: https://github.com/spring-projects-experimental/spring-boot-migrator/pull/777/files#diff-f3362ff9066efd77e7727c970892542c62437c2340439773fde412786623bbd4
Sorry, something went wrong.
Oh nice catch @murdos In my project, I don't use GenericContainer so that's why I'm fine, and for existing modules, there is no use of it
Let's close this, as it's not so important to fix it, and it will be fixed automatically one day, I think :)
No branches or pull requests
When there is
testcontainers
dependency, there are 2 junit dependencies. The results in IDE are:To avoid this, we should exclude junit:
The text was updated successfully, but these errors were encountered: