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

Inconsistent shading of asynchttpclient #862

Closed
bulkazszynka opened this issue Mar 7, 2024 · 5 comments · Fixed by #863
Closed

Inconsistent shading of asynchttpclient #862

bulkazszynka opened this issue Mar 7, 2024 · 5 comments · Fixed by #863

Comments

@bulkazszynka
Copy link

bulkazszynka commented Mar 7, 2024

2.X line of the playframework includes the asynchttpclient library having packages prefixed with play.shaded.ahc. However, in version 3.0 this prefix has been removed from 3 class files i.e.

  • com.typesafe.netty.CancelledSubscriber
  • com.typesafe.netty.HandlerPublisher
  • com.typesafe.netty.HandlerSubscriber

Such inconsistency may lead to compatibility issues for users who upgrade from version 2.9 to 3.0.

@mkurz mkurz transferred this issue from playframework/playframework Mar 7, 2024
@mkurz
Copy link
Member

mkurz commented Mar 7, 2024

Hmm.. Yes I can confirm this is incorrect... Not sure why the play.shaded.ahc. prefix gets removed here...
Actually, the package name in Play 3 changed to org.playframework.netty so what the package really should be is:

  • play.shaded.ahc.org.playframework.netty.CancelledSubscriber
  • play.shaded.ahc.org.playframework.netty.HandlerPublisher
  • play.shaded.ahc.org.playframework.netty.HandlerSubscriber

Actually I though 0efba3c does take care of that, not sure why this does not work.

But yes this needs to be checked and fixed.
Thanks for the report!

@mkurz mkurz linked a pull request Mar 7, 2024 that will close this issue
@mkurz mkurz closed this as completed in #863 Mar 7, 2024
@mkurz
Copy link
Member

mkurz commented Mar 7, 2024

Actually my last comment was not entirely correct, the correct package name still should be com.typesafe.netty prefixed with play.shaded.ahc.*, resulting in play.shaded.ahc.com.typesafe.netty.*. Fixed in now in # #863, see comments over there for more explanation.

@SheliakLyr
Copy link

Hi. We are also impacted by this problem. Is there a release planned with the fix?

@mkurz
Copy link
Member

mkurz commented Mar 12, 2024

Hi. We are also impacted by this problem. Is there a release planned with the fix?

Actually there is nothing holding back a new patch release, so I can do that now.

@mkurz
Copy link
Member

mkurz commented Mar 12, 2024

3.0.2 released: https://github.com/playframework/play-ws/releases/tag/3.0.2

If you are using the Play Framework, you can upgrade yourself until Play 3.0.3 is released:

...
libraryDependencies += ws // or javaWs

// Use latest play-ws release (can be removed when Play 3.0.3 is released)
val playWS = "3.0.2"
libraryDependencies ++= Seq(
  "org.playframework" %% "play-ahc-ws-standalone" % playWS,
  "org.playframework" %% "play-ws-standalone-json" % playWS,
  "org.playframework" %% "play-ws-standalone-xml" % playWS,
  "org.playframework" % "shaded-asynchttpclient" % playWS,
  "org.playframework" % "shaded-oauth" % playWS,
)
...

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.

3 participants