[
https://issues.apache.org/jira/browse/HIVE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu updated HIVE-5733:
------------------------------------------
Attachment: HIVE-5733.1.patch
As per the documentation of maven-shade-plugin the plugin will replace the
project's main artifact with the shaded artifact. Giving a different classifier
like nodep also was not helpful. As per the doc, the shaded artifact can be
given a different name. Doc -
http://maven.apache.org/plugins/maven-shade-plugin/examples/attached-artifact.html
Attaching the patch which generates hive-exec-<version>.jar with no
dependencies and hive-exec-<version>.-withdep.jar as the shaded jar.
> Publish hive-exec artifact without all the dependencies
> -------------------------------------------------------
>
> Key: HIVE-5733
> URL: https://issues.apache.org/jira/browse/HIVE-5733
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Jarek Jarcec Cecho
> Assignee: Amareshwari Sriramadasu
> Attachments: HIVE-5733.1.patch
>
>
> Currently the artifact {{hive-exec}} that is available in
> [maven|http://search.maven.org/remotecontent?filepath=org/apache/hive/hive-exec/0.12.0/hive-exec-0.12.0.jar]
> is shading all the dependencies (= the jar contains all Hive's
> dependencies). As other projects that are depending on Hive might be use
> slightly different version of the dependencies, it can easily happens that
> Hive's shaded version will be used instead which leads to very time consuming
> debugging of what is happening (for example SQOOP-1198).
> Would it be feasible publish {{hive-exec}} jar that will be build without
> shading any dependency? For example
> [avro-tools|http://search.maven.org/#artifactdetails%7Corg.apache.avro%7Cavro-tools%7C1.7.5%7Cjar]
> is having classifier "nodeps" that represents artifact without any
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
