[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058468#comment-14058468
]
Shwetha G S commented on OOZIE-1876:
------------------------------------
{quote}
I don't think we want to do that because if you do a mvn clean, it will delete
the tomcat tarball and you'd have to re-download it.
{quote}
For some reason, I thought the build was downloading tomcat every time. Thats
why I moved it to target. Will revert that
{quote}
I'm afraid this will break things nastily when consuming Oozie artifacts from a
Maven repo as profiles don't have an effect on dependencies.
{quote}
[~tucu00], The reason for this is aggregation jars like oozie-hadoop. If the
modules depend on hadoop jars directly(through profiles) instead of
oozie-hadoop, it should work always. Do you see any issue with that?
> 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)
