[
https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219365#comment-13219365
]
Roman Shaposhnik commented on BIGTOP-417:
-----------------------------------------
After spending some time reviewing the versions and availability of Tomcat for
the platforms we have to support I'm leaning towards a solution of making
tomcat be part of the Bigtop distribution itself. That will help us get around
a sad state of affairs on platforms like CentOS 5 (where only Tomcat 5 is
available, and Oozie/HTTPFS need at least 6) and also give a greater control
over the versioning of Tomcat in general (we can keep it uniform across all the
distros).
Of course, we will not be a producing a general-purpose Tomcat packaging
solution here. Think of it as an "embedded Tomcat" or as a Bigtop Container
Platform (BCP). The proposed package name will be bigtop-tomcat and the
location of files will be /usr/lib/bigtop-tomcat. No init.d scripts or /usr/bin
scripts will be provided since the entry point will remain via the init.d
scripts of individual components (e.g. /etc/init.d/{oozie,httpfs}).
Thoughts?
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
>
> We now have at least 2 different components that squirrel away private copies
> of Tomcat (Oozie and HTTPFS). The right approach is to setup different
> instances of the system Tomcat via CATALINA_BASE (still pointing at a common,
> system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
