You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Attila Sasvari (JIRA)" <ji...@apache.org> on 2016/12/05 21:49:58 UTC

[jira] [Updated] (OOZIE-2741) Remove Tomcat

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

Attila Sasvari updated OOZIE-2741:
----------------------------------
    Attachment: OOZIE-2741-2.patch

>  Remove Tomcat
> --------------
>
>                 Key: OOZIE-2741
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2741
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Attila Sasvari
>            Assignee: Attila Sasvari
>         Attachments: OOZIE-2741-1.patch, OOZIE-2741-2.patch, OOZIE-2741-3.patch
>
>
> Supporting both embedded Oozie and Tomcat makes things unnecessarily complicated.
> Some benefits of removing Tomcat:
> - Removing the new Tomcat profile completely that OOZIE-2666 introduces  would make easier to understand how to build Oozie.
> - Cleaner and simpler packaging (and starting scripts) -  we wouldn't need to deal with any war repackaging scripts, or special scripts for turning on SSL (this what we currently need to do when using Tomcat). Also we could get rid of assembly xml for tomcat.
> ??Note: We can still support building a WAR file for users who want to deploy Oozie in their own (not embedded) Tomcat or Jetty. So if someone wants to use Tomcat, they can deploy a Tomcat server and use the WAR file.??
> h5. Main tasks
> - Remove tomcat profile completely
> - distro: pom and shell scripts
> - src /main / assemblies distro-tomcat.xml



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