[
https://issues.apache.org/jira/browse/HIVE-28455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875429#comment-17875429
]
Stamatis Zampetakis commented on HIVE-28455:
--------------------------------------------
It is a bad practice for a single module to publish multiple jars since there
is no way to publish multiple pom files for the same module. In the presence of
multiple jars we have to decide what is the main artifact that should be used
in dependent components and fix things accordingly.
> Missing dependencies due to upgrade of maven-shade-plugin
> ---------------------------------------------------------
>
> Key: HIVE-28455
> URL: https://issues.apache.org/jira/browse/HIVE-28455
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 4.0.0, 4.0.0-beta-1, 4.1.0
> Reporter: Kokila N
> Assignee: Kokila N
> Priority: Major
> Labels: hive-4.0.1-must
>
> For, hive jdbc , we create two jars {{hive-jdbc}} and
> {{hive-jdbc-standalone}} (shaded jar/uber jar).
> *Reason for change in pom :*
> Due to the changes in the maven code after version 3.2.4, when we create a
> shaded jar ( {{{}hive-jdbc-standalone{}}}), {{dependency-reduced-pom.xml}}
> is generated and dependencies that have been included into the uber JAR will
> be removed from the {{<dependencies>}} section of the generated POM to avoid
> duplication. This {{dependency-reduced-pom.xml}} is why the dependencies are
> removed from the pom as its common for both {{hive-jdbc}} and
> {{{}hive-jdbc-standalone{}}}. So, currently for hive-jdbc , the transitive
> dependencies for it are not propagated.
> Same applies to hive-beeline and hive-exec modules as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
