[
https://issues.apache.org/jira/browse/OOZIE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1358:
---------------------------------
Attachment: OOZIE-1358.patch
The patch updates oozie-setup.sh and addtowar.sh to handle either extjs 2.2 or
2.3.0. We have to hardcode some paths in webapp's oozie-console.js and
index.html so in order to support either version of extjs, I've also made the
scripts rename the ext-2.2 or ext-2.3.0 dir to simply ext.
Obviously no unit tests, but I verified that both scripts can use properly
handle either version of extjs. I also ran some jobs and clicked on a lot of
different things in the UI to make sure it still works correctly with 2.3.0.
It would be good if a few others can try the scripts and also using the Web UI
with 2.3.0 to double check that I didn't miss any edge cases.
Also, [~virag], is this something we want in branch-4 also? It may require a
slightly different patch because of the changes to the scripts.
> extjs 2.2 is no longer available; we should switch to extjs 2.3.0
> -----------------------------------------------------------------
>
> Key: OOZIE-1358
> URL: https://issues.apache.org/jira/browse/OOZIE-1358
> Project: Oozie
> Issue Type: Bug
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Fix For: trunk, 4.0.0
>
> Attachments: OOZIE-1358.patch
>
>
> As reported by a user on the mailing list,
> http://extjs.com/deploy/ext-2.2.zip is not longer available. I couldn't find
> an official alternate link anywhere and there's no mention of it on their
> website.
> I tried the latest version, which was much bigger, but it didn't work. Using
> the earliest version that they do mention, 2.3.0, seems to work; so I think
> we should update the docs to point to
> http://dev.sencha.com/deploy/ext-2.3.0.zip and update the scripts to look for
> either version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
