Source code for shaded jars are not properly published along with the shaded jars

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

package play.shaded.ahc.io.netty.channel.nio;
...
public abstract class AbstractNioChannel extends AbstractChannel {

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

$ cd netty
$ mkdir -p transport/src/main/java/play/shaded/ahc
$ cp -a transport/src/main/java/io transport/src/main/java/play/shaded/ahc/.
$ find transport/src/main/java/play/shaded/ahc -name "*.java" -exec sed -i 's#package io\.#package play.shaded.ahc.io.#' {} \; -exec sed -i 's#import io\.#import play.shaded.ahc.io.#' {} \; -exec sed -i 's#import static io\.#import static play.shaded.ahc.io.#' {} \;

Originally posted by @jhooda in https://github.com/playframework/play-ws/issues/85#issuecomment-1130406025

Start by inspecting the shaded artifact contents at the Maven repository URL and the Netty path transport/src/main/java mentioned in the workaround. Verify how shaded packages are represented in the published source archive; done means the source files match the shaded class packages so a debugger can bind to them.