[
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701463#comment-13701463
]
Bruno Mahé commented on BIGTOP-939:
-----------------------------------
{quote}There are already more examples of this kind of thing in a certain
distribution downstream of Bigtop, which leads me to believe these kinds of
things will likely continue to come up.{quote}
Your patch makes sense, but this becoming a pattern is exactly why I am trying
to be more careful.
I will try to build a package with your patch and look more into it.
In the mean time:
* Why not having a static symlink to /etc and have people use alternatives to
switch between ssh/no-ssl configs?
* {noformat}
+ if [ -e ${DEPLOYMENT_TARGET} ] ; then
+ rm -r ${DEPLOYMENT_TARGET}
+ fi
{noformat}
Shouldn't the _rm_ command have also a _-f_ parameter?
> 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
>
>
> 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
