thswlsqls opened a new pull request, #8683:
URL: https://github.com/apache/paimon/pull/8683
### Purpose
close #6682
- The Spark 4 modules (`paimon-spark4-common`, `paimon-spark-4.0`,
`paimon-spark-4.1`) hardcode `_2.13` in their `artifactId` but resolve
dependencies via `${scala.binary.version}`, which defaults to `2.12` and is
only set to `2.13` by the `spark4` profile.
- With the profile inactive (external consumers of the published POMs, or a
direct module build), they resolve `_2.12` artifacts that either do not exist
or mix Scala 2.12 and 2.13 on the classpath.
- Spark 4 is Scala-2.13-only, so pin `scala.binary.version=2.13` in each
module. This completes the partial fix in stale PR #6683 (`paimon-spark-4.0`
only).
### Tests
- No unit test: a Maven coordinate-resolution fix with no runtime behavior
to assert (cf. POM fixes #8560, #8555).
- `help:effective-pom` with `spark4` **inactive**: every
`paimon-spark*`/`spark-*` coordinate now resolves to `_2.13` (was `_2.12`).
No-op when the profile is active; Spark `*ITCase` covered by CI.
--
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]
