-
Notifications
You must be signed in to change notification settings - Fork 85
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
shaded asynchttpclient sources are not published #85
Comments
fixed |
Okay, not fixed, but the sources is org.asynchttpclient |
hmm... yeah, problem is debugging issues related to plays ws client that way.. the underlying problem seems to be, that the shading happens on bytecode level... just noticed this when I tried to replace those constants I'll see if I find a adequate solution for that. |
The problem is when attaching debugger with a running process using any shaded library. The non-shaded source code won't bind with the shaded classes that belong to the shaded packages such as
The source code is still 266 bytes, see, https://repo1.maven.org/maven2/com/typesafe/play/shaded-asynchttpclient/2.1.3/ So any plan to correctly publish shaded sources? A workaround in case someone needs it
|
@jhooda Please open a new issue for that, thanks! |
shaded-asynchttpclient-1.0.0-M4-sources.jar is only 256 bytes big and contains only the manifest.mf file.
The text was updated successfully, but these errors were encountered: