falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-961) Remove build-oozie.sh
Date Tue, 23 Dec 2014 01:25:13 GMT

    [ https://issues.apache.org/jira/browse/FALCON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256418#comment-14256418

Srikanth Sundarrajan commented on FALCON-961:

[~sureshms], build-oozie script is achieving the following things now.

1. Make oozie artifacts available in local repo for falcon builds to use
2. Patch oozie with features that are still in oozie-trunk, but falcon is dependent on
3. Create a oozie distro that we expect falcon users to use if we have additional patches
over the latest release version

Publishing oozie artifacts in maven repo will surely address and eliminate the need for #1,
items #2 & #3 are still required and deprecating build-oozie.sh may not be possible.

> 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

View raw message