-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Upgrade Reactor to 2.0.x #2719
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
Comments
We need to consider this carefully given that's it a breaking change and Spring Framework currently has an optional dependency on the old one. |
Actually, it might be worth adding a JIRA to see what the plan is for Spring 4.2. |
And there's also XD to consider. |
That's really a requirement from XD. |
I think that both can co-exist but we still need to make the decision about if we should remove v1 from |
FYI we are in consolidation phase (2.0.1) so if you guys upgrade to 2.0.0.RELEASE in spring.io that will be great to verify any pending issue before the candidate we think for Maven Central: 2.0.1 |
@smaldini We've not worked on the upgrade yet so I don't think we have anything to test yet I'm afriad. |
Spring Framework 4.2 is now compiling against Reactor 2.0.1 snapshots so now's a good time for us to do the same |
Feel free to ping me if you need, also 2.0.1 is around the corner, pending Reactive Streams 1.0 final imminent (reactive-streams/reactive-streams-jvm#223). |
Boot's 1.3.0 snapshots are now building successfully against Reactor's 2.0.1 snapshots |
No description provided.
The text was updated successfully, but these errors were encountered: