[
https://issues.apache.org/jira/browse/FELIX-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4683.
----------------------------------
Resolution: Fixed
Added a "org.apache.felix.dependencymanager.shell.scope" bundle context
property, which can be used to configure the DM shell commands scope (by
default, the scope is "dependencymanager").
> Allow to configure the DependencyManager shell scope
> ----------------------------------------------------
>
> Key: FELIX-4683
> URL: https://issues.apache.org/jira/browse/FELIX-4683
> Project: Felix
> Issue Type: Wish
> Components: Dependency Manager
> Affects Versions: dependencymanager.shell-4.0.0
> Reporter: Pierre De Rop
> Assignee: Pierre De Rop
> Priority: Minor
> Fix For: dependencymanager.shell-4.0.0
>
>
> When using both DependencyManager 3.2.0 and 4.0.0 in the same jvm framework,
> there is a problem when using both shells for the two DM versions, because
> there is a clash between the two dm shell commands scope
> ("dependencymanager").
> So, in order to be able to use both shells (for 3.2.0 and 4.0.0), it should
> be possible to configure from the bundle context the name of the scope used
> by the dm shell.
> For example:
> {code}
> org.apache.felix.dependencymanager.shell.scope=dm4
> {code}
> Then both shell versions could be used in the same framework:
> {code}
> g! help
> dependencymanager:dm
> dm4:dm
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
