thswlsqls opened a new issue, #8937: URL: https://github.com/apache/paimon/issues/8937
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ 6464ef301 / 2.0-SNAPSHOT (also present in released 1.2.0) **Compute Engine** Engine-agnostic (filesystem plugin loader) **Minimal reproduce step** Add `org.apache.paimon:paimon-gs:1.2.0` as a dependency and run `mvn dependency:tree`: `paimon-common` (and its transitives) appears at compile scope — unlike any sibling loader. Cause: `paimon-filesystems/paimon-gs/pom.xml` declares `paimon-common` without a scope (line 37-41) and `paimon-gs-impl` without `<optional>true</optional>` (line 50-61). All 7 sibling loaders (s3/oss/obs/cosn/azure/jindo/jindodls) declare `paimon-common` as `provided`, and the 5 PluginFileIO siblings mark the impl dependency optional. **What doesn't meet your expectations?** Expected: the published paimon-gs pom follows the sibling loader contract — `paimon-common` is supplied by the Paimon engine bundle at runtime, not leaked to consumers. Actual: Maven Central `paimon-gs-1.2.0.pom` publishes `paimon-common` at compile scope, pulling unshaded core classes that duplicate and can version-skew against the engine bundles. **Anything else?** The drift comes from #5238, which copied the cosn pom but dropped these two lines. **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
