vinishjail97 opened a new pull request, #996:
URL: https://github.com/apache/incubator-xtable/pull/996
`xtable-spark-runtime` shades the `xtable-spark-extensions` classes in, and
its published (dependency-reduced) pom declares no `org.apache.xtable`
dependencies. Users load the SQL extensions from the runtime jar, so the thin
`xtable-spark-extensions_2.12` jar does not need to go to Maven Central.
- **`xtable-spark-extensions/pom.xml`:** skips `maven-deploy-plugin`, the
same way `xtable-utilities` does. The module still builds and installs locally,
so `xtable-spark-runtime` can shade it.
- **`release/scripts/validate_staged_bundles.sh`:**
- checks `xtable-spark-runtime_2.12` in the staging repo
- fails on a missing artifact. The script ran `e.xit 1`, so it printed the
miss and still passed.
`xtable-aws`, `xtable-hive-metastore` and `xtable-service` also deploy and
are not in the staged bundle list. They are left for a follow-up.
**Testing:**
- With `-DdeployArtifacts=true`, the effective pom of
`xtable-spark-extensions` shows `<skip>true</skip>` on `default-deploy`.
- `validate_staged_bundles.sh` against a staging repo that does not exist
now exits 1 on the first missing artifact.
- `apache-rat:check`, `validate_shaded_license_coverage.sh` and
`validate_bundled_license_texts.py` pass on all four shaded bundles. The
`xtable-spark-runtime` jar is 4.4 MB.
--
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]
