-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
implementation scope for junit4 #10283
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
implementation scope for junit4 #10283
Conversation
|
Hi, thanks for your contribution. Have you tested the changes? Previous to this changes, <dependencies>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers</artifactId>
<version>1.21.1</version>
<scope>compile</scope>
</dependency>
</dependencies>Now, it has <dependencies>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers</artifactId>
<version>1.21.2-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>5.10.3</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-api</artifactId>
<version>5.10.3</version>
<scope>runtime</scope>
</dependency>
</dependencies>which fails because of Also, I've tried different approaches in the past and it was not easy to remove the dependency without breaking changes. |
|
Hi, I think it would be more straightforward to use standard gradle way of building pom.xml instead of manual operations (not sure why it's like that currently), then we can have more control. Let me try that first. Where can you see the |
|
Thanks for your contribution. We have decided to drop support for JUnit 4. See #10805 |
Currently junit4 has api scope, so it will be visible outside
And then projects using junit 5 will see 2
@Testannotations, which can cause problems - #970After this change
TestRule- then it would need compile/test dependency on junit4