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 Wed, 24 Dec 2014 02:31:13 GMT

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

Srikanth Sundarrajan commented on FALCON-961:

[~sureshms], I understand that we have been able to get all the additional patches that falcon
depends on into 4.1.0. Though the plate looks clean now, Are we sure we are not going to need
additional patches over trunk in future either ? 

Also the falcon el extensions aren't available in the public oozie, wouldn't the process in
integration tests which are referring to new el functions fail on submission? It is possible
that the tests are succeeding because we dont quite wait to see if the coord actually started
or not, but with this change, I guess they would be failing.

> 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
>         Attachments: FALCON-961.patch
> 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