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

Should we keep mutiny-reactive-streams-operators in this repo? #985

Closed
jponge opened this issue Jul 11, 2022 · 3 comments · Fixed by #990
Closed

Should we keep mutiny-reactive-streams-operators in this repo? #985

jponge opened this issue Jul 11, 2022 · 3 comments · Fixed by #990

Comments

@jponge
Copy link
Member

jponge commented Jul 11, 2022

See $title 😉

We have 3 options:

  1. keep it in this repository, but pin the mutiny-reactive-streams-operators project Mutiny version to 1.x stable
  2. move to another smallrye repo
  3. remove from the main branch and consider that the code will be maintained in the 1.x branch
@jponge jponge added this to the 2.0.0 milestone Jul 11, 2022
@jponge
Copy link
Member Author

jponge commented Jul 12, 2022

Or... 4 migrate to Mutiny 2.0 (but shift the baseline)

@cescoffier
Copy link
Contributor

We will have to migrate the implementation to mutiny 2.0 and so use lots of adaptation.
This is mainly because this module is required in reactive messaging, and so we need a version using the latest mutiny version. Without it, we will end up with two versions of mutiny on the classpath (which leads to package name changes and so on).

@cescoffier
Copy link
Contributor

To answer the $title question: yes.

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 a pull request may close this issue.

2 participants