[
https://issues.apache.org/jira/browse/KARAF-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149056#comment-13149056
]
Jean-Baptiste Onofré commented on KARAF-969:
--------------------------------------------
I don't thank that using a fully qualified name will help.
An user can still define the same feature name (even if it's full qualified) in
two different features XML.
In the feature validation util, we can check if a feature with the same name
AND version exists. If it's the case, we should raise an exception.
I'm not in favor of using features:install <repo>:<feature> because the user
shouldn't take care of the repo itself.
> 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
