[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238719#comment-14238719
]
Rohini Palaniswamy commented on OOZIE-1876:
-------------------------------------------
[~shwethags],
This would impact how we have been doing deploys as we can have different
versions of hadoop/hcat/hbase deployed on different clusters and we need to
inject the jars deployed on that cluster into the war. A static war file would
not work in a environment where other components(hbase/hive/hcat) are upgraded
independently. Could you make packaging the libraries into war file as a new
maven option instead and leave the old behavior as it is?
> 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-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)
