[
https://issues.apache.org/jira/browse/FALCON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257480#comment-14257480
]
Suresh Srinivas commented on FALCON-961:
----------------------------------------
[~sriksun], couple of comments.
Currently with oozie 4.1.0, all the exceptions that Falcon tracks is covered.
Is it not?
bq. Patch oozie with features that are still in oozie-trunk, but falcon is
dependent on
This will not be required if oozie builds are made available in nexus repo. Do
you agree?
bq. Create a oozie distro that we expect falcon users to use if we have
additional patches over the latest release version
Are there many such exceptions? This exception can be done by the users instead
of supporting this code in Falcon.
> Remove build-oozie.sh
> ---------------------
>
> Key: FALCON-961
> URL: https://issues.apache.org/jira/browse/FALCON-961
> Project: Falcon
> Issue Type: Bug
> Components: build-tools
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
>
> Oozie artifacts are published in maven central for release 4.1.0, thanks to
> [~bowenzhangusa] the release manager for that release. With this,
> build-oozie.sh is no longer needed. This jira proposes removing that script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
