Venkata Sai Akhil Gudesa created SPARK-41967:
------------------------------------------------
Summary: SBT unable to resolve particular packages from the
imported maven build
Key: SPARK-41967
URL: https://issues.apache.org/jira/browse/SPARK-41967
Project: Spark
Issue Type: Bug
Components: Connect
Affects Versions: 3.4.0
Reporter: Venkata Sai Akhil Gudesa
An SBT issue causes the resolution from the imported maven build for particular
packages to not work for an unknown reason. This affects Spark-Connect-related
projects (see
[here|https://github.com/apache/spark/blob/6cae6aa5156655c79eb3f20292ccec6c479c3b1b/project/SparkBuild.scala#L667-L668]
and
[here|https://github.com/apache/spark/blob/6cae6aa5156655c79eb3f20292ccec6c479c3b1b/project/SparkBuild.scala#L902-L904]
for example) by forcing duplicate deps.
The pom build works fine when removing the affected dep (like guava for
example) but the sbt build then fails. Thus, we are forced to explicitly
mention the versions of the affected packages so that SBT can then parse the
version(s) to manually include them (and they're also added as a dep in maven
to ensure version consistency with sbt)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
