Skip to content
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

Reconsider and possibly remove reactive-streams-junit5-tck #942

Closed
jponge opened this issue Jun 2, 2022 · 0 comments · Fixed by #981
Closed

Reconsider and possibly remove reactive-streams-junit5-tck #942

jponge opened this issue Jun 2, 2022 · 0 comments · Fixed by #981
Labels
api-deprecation API deprecation or removal on-roadmap The issue is part of the roadmap

Comments

@jponge
Copy link
Member

jponge commented Jun 2, 2022

This module offers a JUnit5 shim around the reactive streams TCK, but we've recently switched back to the plain RS TCK written for TestNG as a JUnit5 runner for TestNG exists, allowing both JUnit 4 / 5 / TestNG tests to co-exist.

According to https://mvnrepository.com/artifact/io.smallrye.reactive/reactive-streams-junit5-tck/usages it looks like usages are limited to:

  • mutiny-context-propagation
  • smallrye-reactive-messaging-kafka
  • mutiny-smallrye-context-propagation
@jponge jponge added on-roadmap The issue is part of the roadmap api-deprecation API deprecation or removal labels Jun 2, 2022
@jponge jponge added this to the 2.0.0 milestone Jun 2, 2022
@jponge jponge linked a pull request Jul 7, 2022 that will close this issue
@jponge jponge modified the milestones: 2.0.0, 2.0.0-milestone1 Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-deprecation API deprecation or removal on-roadmap The issue is part of the roadmap
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant