You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2012/06/29 19:08:44 UTC
[jira] [Created] (KARAF-1600) Avoid duplicate feature and bundle
resolution when installing cascading features
Raul Kripalani created KARAF-1600:
-------------------------------------
Summary: Avoid duplicate feature and bundle resolution when installing cascading features
Key: KARAF-1600
URL: https://issues.apache.org/jira/browse/KARAF-1600
Project: Karaf
Issue Type: Improvement
Affects Versions: cellar-2.2.2
Reporter: Raul Kripalani
Currently, if one has multiple features depending on each other, where the same features or bundles are referenced twice or more, Karaf will attempt to resolve/install them as many times as they are traversed.
E.g., pseudo-code:
{code}
feature a, contains:
feature camel-core
feature camel-spring
bundle 1
bundle 2
feature b, contains:
feature camel-jetty
feature camel-http
bundle 3
bundle 4
feature all, contains:
feature a
feature b
{code}
When one installs feature "all", Karaf will end up resolving/attempting to install camel-core multiple times as it hits it via transitive dependencies (via a, via camel-jetty, via camel-http, etc.).
As a result, an unnecessary delay is experienced and this could be optimised to perform a two-phase feature installation procedure instead:
- calculate the install plan (kind of like building an effective POM in Maven) and prune duplicates
- perform the install plan
--
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
[jira] [Resolved] (KARAF-1600) Avoid duplicate feature and bundle
resolution when installing cascading features
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1600.
-----------------------------------------
Resolution: Fixed
> Avoid duplicate feature and bundle resolution when installing cascading features
> --------------------------------------------------------------------------------
>
> Key: KARAF-1600
> URL: https://issues.apache.org/jira/browse/KARAF-1600
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.2.8
> Reporter: Raul Kripalani
> Assignee: Gert Vanthienen
> Labels: features
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> Currently, if one has multiple features depending on each other, where the same features or bundles are referenced twice or more, Karaf will attempt to resolve/install them as many times as they are traversed.
> E.g., pseudo-code:
> {code}
> feature a, contains:
> feature camel-core
> feature camel-spring
> bundle 1
> bundle 2
> feature b, contains:
> feature camel-jetty
> feature camel-http
> bundle 3
> bundle 4
> feature all, contains:
> feature a
> feature b
> {code}
> When one installs feature "all", Karaf will end up resolving/attempting to install camel-core multiple times as it hits it via transitive dependencies (via a, via camel-jetty, via camel-http, etc.).
> As a result, an unnecessary delay is experienced and this could be optimised to perform a two-phase feature installation procedure instead:
> - calculate the install plan (kind of like building an effective POM in Maven) and prune duplicates
> - perform the install plan
--
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
[jira] [Resolved] (KARAF-1600) Avoid duplicate feature and bundle
resolution when installing cascading features
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1600.
-----------------------------------------
Resolution: Fixed
> Avoid duplicate feature and bundle resolution when installing cascading features
> --------------------------------------------------------------------------------
>
> Key: KARAF-1600
> URL: https://issues.apache.org/jira/browse/KARAF-1600
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.2.8
> Reporter: Raul Kripalani
> Assignee: Gert Vanthienen
> Labels: features
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> Currently, if one has multiple features depending on each other, where the same features or bundles are referenced twice or more, Karaf will attempt to resolve/install them as many times as they are traversed.
> E.g., pseudo-code:
> {code}
> feature a, contains:
> feature camel-core
> feature camel-spring
> bundle 1
> bundle 2
> feature b, contains:
> feature camel-jetty
> feature camel-http
> bundle 3
> bundle 4
> feature all, contains:
> feature a
> feature b
> {code}
> When one installs feature "all", Karaf will end up resolving/attempting to install camel-core multiple times as it hits it via transitive dependencies (via a, via camel-jetty, via camel-http, etc.).
> As a result, an unnecessary delay is experienced and this could be optimised to perform a two-phase feature installation procedure instead:
> - calculate the install plan (kind of like building an effective POM in Maven) and prune duplicates
> - perform the install plan
--
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
[jira] [Updated] (KARAF-1600) Avoid duplicate feature and bundle
resolution when installing cascading features
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated KARAF-1600:
-----------------------------------
Affects Version/s: (was: cellar-2.2.2)
2.2.8
Fix Version/s: 3.0.0
2.3.0
2.2.9
Assignee: Gert Vanthienen
Fixed in
- https://svn.apache.org/viewvc?view=revision&revision=1371246 for trunk
- https://svn.apache.org/viewvc?view=revision&revision=1371248 for karaf-2.3.x
- https://svn.apache.org/viewvc?view=revision&revision=1371251 for karaf-2.2.x
> Avoid duplicate feature and bundle resolution when installing cascading features
> --------------------------------------------------------------------------------
>
> Key: KARAF-1600
> URL: https://issues.apache.org/jira/browse/KARAF-1600
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.2.8
> Reporter: Raul Kripalani
> Assignee: Gert Vanthienen
> Labels: features
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> Currently, if one has multiple features depending on each other, where the same features or bundles are referenced twice or more, Karaf will attempt to resolve/install them as many times as they are traversed.
> E.g., pseudo-code:
> {code}
> feature a, contains:
> feature camel-core
> feature camel-spring
> bundle 1
> bundle 2
> feature b, contains:
> feature camel-jetty
> feature camel-http
> bundle 3
> bundle 4
> feature all, contains:
> feature a
> feature b
> {code}
> When one installs feature "all", Karaf will end up resolving/attempting to install camel-core multiple times as it hits it via transitive dependencies (via a, via camel-jetty, via camel-http, etc.).
> As a result, an unnecessary delay is experienced and this could be optimised to perform a two-phase feature installation procedure instead:
> - calculate the install plan (kind of like building an effective POM in Maven) and prune duplicates
> - perform the install plan
--
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
[jira] [Commented] (KARAF-1600) Avoid duplicate feature and bundle
resolution when installing cascading features
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432581#comment-13432581 ]
Jean-Baptiste Onofré commented on KARAF-1600:
---------------------------------------------
As Gert fixed it on all branches (thanks a lot Gert), I resolve this Jira.
> Avoid duplicate feature and bundle resolution when installing cascading features
> --------------------------------------------------------------------------------
>
> Key: KARAF-1600
> URL: https://issues.apache.org/jira/browse/KARAF-1600
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.2.8
> Reporter: Raul Kripalani
> Assignee: Gert Vanthienen
> Labels: features
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> Currently, if one has multiple features depending on each other, where the same features or bundles are referenced twice or more, Karaf will attempt to resolve/install them as many times as they are traversed.
> E.g., pseudo-code:
> {code}
> feature a, contains:
> feature camel-core
> feature camel-spring
> bundle 1
> bundle 2
> feature b, contains:
> feature camel-jetty
> feature camel-http
> bundle 3
> bundle 4
> feature all, contains:
> feature a
> feature b
> {code}
> When one installs feature "all", Karaf will end up resolving/attempting to install camel-core multiple times as it hits it via transitive dependencies (via a, via camel-jetty, via camel-http, etc.).
> As a result, an unnecessary delay is experienced and this could be optimised to perform a two-phase feature installation procedure instead:
> - calculate the install plan (kind of like building an effective POM in Maven) and prune duplicates
> - perform the install plan
--
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