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
[WIP] Remove deprecated scala.concurrent.forkjoin references #18262 #21101
Conversation
Can one of the repo owners verify this patch? |
OK TO TEST |
Test FAILed. |
Is your general workflow for you to schedule looking at this internally? I am not quite sure what should happen next :) The MiMa concerns are valid, which makes me think the MiMa exclusions should only be in effect for 2.5.x?! |
As mentioned in the issue I'm very skeptical to replacing this in a patch release. The behavior or performance profile might have changed. That is too risky to just drop-in to production systems. Feel free to prove me wrong, but then I would like to see evidence that the implementations are almost identical, and I don't have time to do that investigation myself. I have no problem switching for Akka 2.5 |
I will do some investigation. Should I find any difference, I will add the MiMa filters for 2.5 |
Looking at the implementations, they do seem to be slightly different. From what I can tell JDK 8 and Scala 2.11 have different versions of JSR166 included, which causes the difference. I will update the PR |
79931e3
to
c7f2bc6
Compare
Test FAILed. |
Test FAILed. |
52144a1
to
def9363
Compare
Test FAILed. |
This now only fails because we are still building a 2.4.x. I added the MIMA filters for 2.5.0. |
Thank you, @NeQuissimus |
Sounds good, I can just re-send it once there is a 2.5 branch. |
This work fixed #18262.
Binary compatibility warnings will need to be addressed, copy from the discussion on #18262:
The following methods and type hierarchies are affected
Raw log: