You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/05/12 00:13:15 UTC

[jira] [Updated] (BIGTOP-939) Make usage of bigtop-tomcat more dynamic

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

Roman Shaposhnik updated BIGTOP-939:
------------------------------------

    Fix Version/s: 0.7.0
    
> Make usage of bigtop-tomcat more dynamic
> ----------------------------------------
>
>                 Key: BIGTOP-939
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-939
>             Project: Bigtop
>          Issue Type: Task
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>             Fix For: 0.7.0
>
>
> Projects like Oozie and Sqoop present some configuration challenges compared to other components because they use Tomcat. Sometimes small tweaks to the configuration or classpath have to be done in a very component-specific way as opposed to tweaking files in /etc/<comp>/conf or /etc/default. In one case, we even have redundant Tomcat deployments for common configurations (Oozie's SSL vs.  non-SSL).
> If the environment for Tomcat was generated more dynamically, we could avoid this redundancy and could allow common features to be configured in more "standard" ways.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira