[jira] [Updated] (OOZIE-2317) Figure out what to do about Tomcat 6 End of Life

["Robert Kanter (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-2317:
---------------------------------
    Description: 
[Tomcat 6 will be end of life on Dec 31 2016.|https://tomcat.apache.org/tomcat-60-eol.html]

Even though that's a quite a while from now, it's best to stay ahead of things, so it would be good if we looked into a plan for this.  

Here are some options:
# Upgrade to Tomcat 7
# Upgrade to Tomcat 8
# Switch to embedded Jetty 9

I imagine upgrading to Tomcat 7/8 would be the easiest solution.  I haven't looked into it much, but I imagine the build and deploy process could remain relatively the same; though we'd probably have to tweak some config files and things.  As for which version, Tomcat has [this page|https://tomcat.apache.org/whichversion.html] to help.

Switching to embedded Jetty 9 would require changing the build and deploy process, though that might be a good thing given how that can be complicated/confusing for users.  And I know Tomcat makes things difficult for our packaging team in Cloudera.  Many other Hadoop projects use embedded Jetty as well.  We do know that Oozie runs properly in Jetty because our unit tests use Jetty.

As part of this JIRA, the assignee should probably look into more specific pros/cons of the options and we should all reach a consensus before moving forward.

  was:
Tomcat 6 will be end of life on Dec 31 2016.

Even though that's a quite a while from now, it's best to stay ahead of things, so it would be good if we looked into a plan for this.  

Here are some options:
# Upgrade to Tomcat 7
# Upgrade to Tomcat 8
# Switch to embedded Jetty 9

I imagine upgrading to Tomcat 7/8 would be the easiest solution.  I haven't looked into it much, but I imagine the build and deploy process could remain relatively the same; though we'd probably have to tweak some config files and things.  As for which version, Tomcat has [this page|https://tomcat.apache.org/whichversion.html] to help.

Switching to embedded Jetty 9 would require changing the build and deploy process, though that might be a good thing given how that can be complicated/confusing for users.  And I know Tomcat makes things difficult for our packaging team in Cloudera.  Many other Hadoop projects use embedded Jetty as well.  We do know that Oozie runs properly in Jetty because our unit tests use Jetty.

As part of this JIRA, the assignee should probably look into more specific pros/cons of the options and we should all reach a consensus before moving forward.


> Figure out what to do about Tomcat 6 End of Life
> ------------------------------------------------
>
>                 Key: OOZIE-2317
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2317
>             Project: Oozie
>          Issue Type: Bug
>          Components: core
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>
> [Tomcat 6 will be end of life on Dec 31 2016.|https://tomcat.apache.org/tomcat-60-eol.html]
> Even though that's a quite a while from now, it's best to stay ahead of things, so it would be good if we looked into a plan for this.  
> Here are some options:
> # Upgrade to Tomcat 7
> # Upgrade to Tomcat 8
> # Switch to embedded Jetty 9
> I imagine upgrading to Tomcat 7/8 would be the easiest solution.  I haven't looked into it much, but I imagine the build and deploy process could remain relatively the same; though we'd probably have to tweak some config files and things.  As for which version, Tomcat has [this page|https://tomcat.apache.org/whichversion.html] to help.
> Switching to embedded Jetty 9 would require changing the build and deploy process, though that might be a good thing given how that can be complicated/confusing for users.  And I know Tomcat makes things difficult for our packaging team in Cloudera.  Many other Hadoop projects use embedded Jetty as well.  We do know that Oozie runs properly in Jetty because our unit tests use Jetty.
> As part of this JIRA, the assignee should probably look into more specific pros/cons of the options and we should all reach a consensus before moving forward.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)