[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101366#comment-14101366
]
Robert Kanter commented on OOZIE-1876:
--------------------------------------
A couple of comments:
# hbaselibs gets deleted and simply made a dependency in oozie-core. I think
this is a good idea (not sure why it was spun out like that before). But it's
scope is set to {{provided}}. Shouldn't it be compile? I believe Oozie only
needs this for HBaseCredentials, so you can probably exclude some things, but I
think we must need some HBase jar in the Oozie server, right?
# core and the hcatalog sharelib depend directly on the hcat artifacts now
instead of oozie-hcatalog; I think this makes sense now that we're only
building one version at a time. However, why do we still need the hcataloglibs
and package it into a new tarball?
> use pom properties rather than specific version numbers in the pom files of
> hbaselibs, hcataloglibs, sharelib, etc
> -------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1876
> URL: https://issues.apache.org/jira/browse/OOZIE-1876
> Project: Oozie
> Issue Type: Improvement
> Components: build
> Affects Versions: 4.0.1
> Reporter: John
> Assignee: Shwetha G S
> Fix For: trunk
>
> Attachments: OOZIE-1876-v2.patch, OOZIE-1876-v3.patch,
> OOZIE-1876-v4.patch, OOZIE-1876-v5.patch, OOZIE-1876.patch
>
>
> version numbers (hbase, hive, hcatalog, sqoop, etc) are hard coded in the pom
> files.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
