Publish a thin jar instead of a jar with all its dependencies

[wangzw]

Since 2.2.9 only the fat jar is published to maven public repository. And it cause the conflict between the classes included into fat jar and third party jar from other vendor.

It cost me the whole afternoon to find the root cause.

[chengww5217]

You mean the source jar whom may be named as qingstor.sdk.java-2.2.9-sources.jar, has no longer been published to the maven public repository since 2.2.9?

[wangzw]

Only 2.2.11-all-deps is published to public repository, but all-deps jar cause conflict with the jar from third-party. For example snakeyaml

https://mvnrepository.com/artifact/com.yunify/qingstor.sdk.java

[wangzw]

The problem caused by all-deps jar is that you not only publish the code of qingstor SDK, you also publish the code which qingstor SDK depends on(packaged in the same jar), which cause the conflict for the user of all-deps jar.

[wangzw]

Please remove all third-party dependency from qingstor SDK jar.

[chengww5217]

I see. You need a jar with none of its dependencies include. That's a nice request.

You know I have been asked to publish the jar all dependencies -- fat jar.

Okay, I'll publish both all dependencies and none dependency jar. Thank you for your feedback.

[chengww5217]

@wangzw Hey bro, a new version 2.2.12 of SDK has been published into the central repository. You can have a try.

PS: from now on, both thin and fat jar versions will be published like our github releases when make a release. If you wanna the fat jar, add the dependency named with version + -all-deps, else named with version.

[wangzw]

Cool, thanks.