[
https://issues.apache.org/jira/browse/OOZIE-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-2254:
---------------------------------
Component/s: (was: site)
core
> Make ext js plugin detection more flexible
> ------------------------------------------
>
> Key: OOZIE-2254
> URL: https://issues.apache.org/jira/browse/OOZIE-2254
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.2
> Reporter: Mark Grover
>
> Currently, oozie expects the ext js module to be installed in a particular
> location under the tomcat root. See this for example:
> https://github.com/apache/oozie/blob/master/webapp/src/main/webapp/index.jsp#L35
> That means that if I have a tarball built and I switch from one tarball to
> another, I have to move my ext module or create a new symlink which is very
> painfully unmaintainable. This is also painful for projects like Apache
> Bigtop where end users have to modify the contents delivered by packages
> (stuff under /usr/lib/oozie) by putting ext module in there or a symlink to
> where it is, in there. This is against best practices as well.
> It would be great if oozie respected a variable that contained the location
> of where the ext module is located and used that instead of always assuming
> it's located in a particular location, if so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
