[
https://issues.apache.org/jira/browse/KARAF-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950840#comment-16950840
]
Sascha Vogt commented on KARAF-6425:
------------------------------------
Yes, for us it would already be enough if it resolves the same every time.
IE. if all other things equal it would start / deploy features alphabetically
or so so at least if it "sometimes" detects some refreshes it always does
making debugging / fixing things easier.
> Provide a "Simple" Features Resolver
> ------------------------------------
>
> Key: KARAF-6425
> URL: https://issues.apache.org/jira/browse/KARAF-6425
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the "full" features resolver is super powerful but some users
> complain about some effect:
> 1. as it can cause refresh, it's not "predictable"
> 2. it's not easy to determine the features/bundles installed due to
> "underlying" caps/reqs resolution
> Even if I think it makes sense to keep the "full" resolver by default, it
> could be interesting to enable a "simple" resolver (configured via
> {{etc/org.apache.karaf.features.cfg}}) looking like what we had in Karaf 2.x:
> more straight forward, just using the content of the feature, and it's up to
> the user to provide complete features (even by hand or by a tool provided by
> Karaf).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
