[jira] [Updated] (KARAF-1169) Support for hidden or dependent features....

["Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>]

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

Jean-Baptiste Onofré updated KARAF-1169:
----------------------------------------

      Description: 
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.







  was:

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.







    Fix Version/s: 3.1.0
         Assignee: Jean-Baptiste Onofré
    
> 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-features
>            Reporter: Daniel Kulp
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.1.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira