[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240363#comment-14240363
]
Robert Kanter commented on OOZIE-1876:
--------------------------------------
This does some major changes to the build, so that's one of the reasons I
wanted to get input from others. For example, in CDH, we ship one set of Oozie
jars, and you can switch between MR1 (Hadoop 1) and MR2 (Hadoop 2) basically by
changing the sharelib and some Tomcat magic; I think Bigtop does something like
this as well. So, as it was before, I'd probably have skipped backporting this
until we drop support MR1 from CDH. And as Rohini pointed out, Y! upgrades
component versions independently.
I think the profile thing should work for us and Yahoo! ([~rohini]?), but I'll
have to try that when I get there. In any case, it should make Apache Oozie
easier to use, which is always good.
+1 from me pending Jenkins
> 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-v10.patch, OOZIE-1876-v2.patch,
> OOZIE-1876-v3.patch, OOZIE-1876-v4.patch, OOZIE-1876-v5.patch,
> OOZIE-1876-v5.patch, OOZIE-1876-v6.patch, OOZIE-1876-v7.patch,
> OOZIE-1876-v7.patch, OOZIE-1876-v8.patch, OOZIE-1876-v9.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.3.4#6332)
