Hi, Sure, go ahead and create a JIRA for it.
I don't think anyone's currently planning on doing any more Oozie 4.x releases, though that could change. We also aren't currently maintaining a separate 4.x branch at the moment, though there was another thread suggesting we do that. At the very least, the patch could be made available on the JIRA for those who want it. Another option, for Oozie 5, is to add a maven profile that does the Tomcat deployment, but with the newer Tomcat; that was actually the original plan, but at the time, there was a lack of interest and it seemed simpler to support one deployment mode, so we dropped it. That said, Oozie 5 does also build a WAR file, which can be deployed in a Tomcat server. - Robert On Wed, Feb 15, 2017 at 10:30 PM, Dongying Jiao <[email protected]> wrote: > Hi: > The default tomcat version is 6.0.47 for oozie 4.3.0. I wonder if there > is any risk or impact to upgrade tomcat version to 7 or 8. Is there any > instruction and suggestion for oozie tomcat upgrade? > I know oozie 5.0.0 will remove tomcat, but as it is not released, if > upgrade tomcat in oozie 4.3.0 is low risk and not a big work, I want to > have a try. > Thank you > > Best Regards, > Dong Ying >
