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

David Jencks commented on KARAF-969:
------------------------------------

In trunk it is very easy to package the same feature into multiple feature 
repositories.  I don't think there's anything wrong with this.  I think the 
obvious solution is to have "fully qualified" feature names that look like what 
everyone is using for bundle symbolic names, e.g. 
org.apache.karaf.feature.MyFeatureName. I know these got removed from trunk, 
but IMO this jira is an example of why they should be put back.
                
> Feature installer should not accept different features with equal names
> -----------------------------------------------------------------------
>
>                 Key: KARAF-969
>                 URL: https://issues.apache.org/jira/browse/KARAF-969
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-features
>    Affects Versions: 2.2.2
>            Reporter: Geert Schuring
>              Labels: duplicate, features, name, namespaces
>             Fix For: 2.2.5
>
>
> The feature installer should reject feature files that contain features with 
> conflicting names. The installer currently allows this, while the install 
> command cannot differentiate between two features with the same name.
> Maybe the concept of feature namespaces would be a good solution. The feature 
> repository name could function as the namespace. The install command should 
> then support something like this:
> {code}
> features:install <repo>:<feature>
> {code}

--
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

        

Reply via email to