[
https://issues.apache.org/jira/browse/OOZIE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686679#comment-15686679
]
Attila Sasvari commented on OOZIE-2741:
---------------------------------------
[~gezapeti] thanks for the review. I also removed {{tomcat}} directory from
{{distro}}. However, it would also make sense to have Tomcat settings (i.e.
ssl-server.xml, server.xml) documented somewhere.
Note: Right now we build WAR file as part of the build (when building the
webapp module). Later in the follow-up jira, WAR generation will be separated
into a different maven profile. We will also need to make sure users can
generate the war file not only for unsecure mode but also for HTTPS enabled
scenarios as well (using either web.xml or ssl-web.xml).
> 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)
