Upgrade to Reactor Dysprosium #670
Comments
|
Sounds good - can you submit a pull request to upgrade RSocket to Dysprosium? |
rstoyanchev
added a commit
to rstoyanchev/rsocket-java
that referenced
this issue
Jul 25, 2019
rstoyanchev
added a commit
to rstoyanchev/rsocket-java
that referenced
this issue
Jul 25, 2019
Closes rsocketgh-670 Signed-off-by: Rossen Stoyanchev <rstoyanchev@pivotal.io>
rstoyanchev
added a commit
to rstoyanchev/rsocket-java
that referenced
this issue
Jul 25, 2019
Closes rsocketgh-670 Signed-off-by: Rossen Stoyanchev <rstoyanchev@pivotal.io>
rstoyanchev
added a commit
to rstoyanchev/rsocket-java
that referenced
this issue
Jul 25, 2019
Closes rsocketgh-670 Signed-off-by: Rossen Stoyanchev <rstoyanchev@pivotal.io>
robertroeser
pushed a commit
that referenced
this issue
Jul 25, 2019
Closes gh-670 Signed-off-by: Rossen Stoyanchev <rstoyanchev@pivotal.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to upgrade
spring-messagingtorsocket-coreversion1.0.0-RC1from0.12.2-RC4I started getting consistent JVM crashes in all integration tests. This is with JDK1.8.0_222-b10.I noticed if I build
rsocket-corewith Dysprosium and use that instead, thenspring-messagingtests are back to green. I don't know why but given Reactor Dysprosium should be ready in time for RSocket Java 1.0.0, is there any reason for RSocket Java not to aim to depend on that? If not, could thedevelopbranch be upgraded to Dysprosium?The text was updated successfully, but these errors were encountered: