[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057280#comment-14057280
]
Shwetha G S commented on OOZIE-1876:
------------------------------------
{quote}
Won't this make it so that you'd have the same oozie-hadoop jar version
regardless of which Hadoop you compiled against (and similarly for some others)?
{quote}
Yes, it will. But a clean full build at root always works(irrespective of
arguments/mvn repo).
{quote}
won't this be problematic for users trying to use these jars?
{quote}
Oozie users(clients) will just depend on oozie-client which doesn't require
hadoop. Oozie developers will use full build, so shouldn't be a problem.
{quote}
and for the maven repo?
{quote}
For full build, its not an issue. Will be problematic for partial builds(build
of single module), which I think is done rarely. One way of solving this is get
rid of aggregation jars(like oozie-hadoop) which is just used as a placeholder
for a group of jars. Instead, we can depend of individual hadoop jars directly
> 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.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)
