[ 
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728100#comment-13728100
 ] 

Sean Mackrory commented on BIGTOP-939:
--------------------------------------

I actually just realized that the other services have additional JARs and 
classes underneath WEB-INF, so splitting the configuration into /etc/ and 
keeping binaries in /lib/ is extremely cumbersome. I think I will leave them 
as-is, and just have Oozie split it up that way, since it's a rather common 
step in the configuration that requires this. I'll make my patch consistent 
across RPM and DEB packages, do a bit more testing and then re-post what I 
think I would like to commit if no other concerns come up.
                
> 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
>            Priority: Blocker
>             Fix For: 0.7.0
>
>         Attachments: 
> 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch, 
> 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch, 
> 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch
>
>
> 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

Reply via email to