-
Notifications
You must be signed in to change notification settings - Fork 39
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
Re-introduce deprecated methods #342
Conversation
e0221be
to
769774b
Compare
For improved binary compatibility with 0.4.0
769774b
to
6a85d84
Compare
@raboof Anything missing, can I help? |
Hmm, looks like we need at least part of
|
Ah, that's only in Play 2.7, that might no longer be relevant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If akka is happy, I am too 👍
@raboof Did you also run Lines 22 to 24 in 8c29624
to 0.4.2, MiMa finds 79 potential problems... Or is the MiMa output not relevant here? (0.4.2 is what akka 2.6.18 is using). |
Well, yes and no: I only ran MiMa against 0.5.0. The differences between 0.4.2 and 0.5.0 were already identified and reviewed, for example in https://github.com/lightbend/ssl-config/pull/302/files#diff-5634c415cd8c8504fdb973a3ed092300b43c4b8fc1e184f7249eb29a55511f91R40 . If we were going for complete safety then we shouldn't have updated ssl-config in Akka at all. On the other hand it is perhaps unlikely that downstream projects other than play-ws were using these API's, so given that it's perhaps OK to break the parts that play-ws 2.8 and later don't touch. |
👍 So let's release 0.6.1 😉 |
it is used in play 2.8 and akka-stream 2.6 as well:
|
@raboof note |
@mkurz I guess those are encountered in code paths that are not necessarily always used in play? will a play-ws release fix those? |
@OlegYch @raboof Sorry for my later answer, I just released play-ws 2.1.10 which should fix the reported problem: https://github.com/playframework/play-ws/releases/tag/2.1.10 |
Without implementation: only for improved binary compatibility
with 0.4.0