[
https://issues.apache.org/jira/browse/BIGTOP-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated BIGTOP-1096:
----------------------------------
Attachment: 0001-BIGTOP-1096.-alternatives-within-the-alternatives-ma.patch
This patch breaks the configuration out so that the tomcat configuration is
parallel to the rest of the configuration. I've tested Oozie and Sqoop
especially, but the layout in all the components appears correct and basic
operations are still working.
Thank you for this idea - now that I've seen it I think this is much cleaner
and safer.
> alternatives within the alternatives-managed sub-directory could be harmful
> ---------------------------------------------------------------------------
>
> Key: BIGTOP-1096
> URL: https://issues.apache.org/jira/browse/BIGTOP-1096
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.7.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.8.0
>
> Attachments:
> 0001-BIGTOP-1096.-alternatives-within-the-alternatives-ma.patch
>
>
> I see that Oozie (at least) today creates a second level alternatives managed
> subdir (tomcat conf) under something that is already managed by an
> alternatives mechanism (oozie conf). This looks like it could be a problem if
> the user switches the top level one (oozie conf).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
