You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2014/05/27 13:40:02 UTC
[jira] [Commented] (KARAF-1169) Support for hidden or dependent
features....
[ https://issues.apache.org/jira/browse/KARAF-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009589#comment-14009589 ]
Guillaume Nodet commented on KARAF-1169:
----------------------------------------
I'll add a hidden="true" flag so that features won't appear in completers and feature:list output (and maybe add a flag on this command to actually display them).
> Support for hidden or dependent features....
> --------------------------------------------
>
> Key: KARAF-1169
> URL: https://issues.apache.org/jira/browse/KARAF-1169
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Reporter: Daniel Kulp
> Assignee: Guillaume Nodet
> Fix For: 4.0.0
>
>
> Some applications we have have blocks of common dependencies that are shared by multiple features. We currently define them in a new feature, but that's not really what they are as it's not expected to be installed individually. Right now, they appear in things like the features:list which can confuse users. We can just put all the bundles in that feature into all the other features that need it, but that duplicates a lot of stuff and can create additional maintenance work.
> There are a couple options that could be pursued:
> 1) Could just add a flag like dependency="true" or abstract="true" or hidden="true" to <feature> to mark the feature as something that shouldn't really be exposed to the user.
> 2) Create a new tag to express common blocks of bundles that can be depended on from a feature.
> For example, CXF has a "cxf-saaj-impl" feature that installs the bundles needed for SAAJ to work. That is then required by ws-security and jaxws and a few others. It's not really something we would expect users to "features:install", but we also don't want to duplicate that setup in a bunch of other places.
--
This message was sent by Atlassian JIRA
(v6.2#6252)