You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/01/07 09:10:00 UTC

[jira] [Created] (KARAF-6577) Be able to define ranking on startupFeature or at least framework feature should be in earliest stage

Jean-Baptiste Onofré created KARAF-6577:
-------------------------------------------

             Summary: Be able to define ranking on startupFeature or at least framework feature should be in earliest stage
                 Key: KARAF-6577
                 URL: https://issues.apache.org/jira/browse/KARAF-6577
             Project: Karaf
          Issue Type: Improvement
          Components: karaf
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: 4.3.0, 4.2.8


Currently the resolver considers all startupFeatures at the same "level". Meaning that if we have prerequisite, it tries to resolve these features in early stage, even before the framework feature.

It causes issue with some features, like jdbc.

At least the framework feature should be the first resolved (whatever prerequisites are) or be able to define ranking/staging attribute on startupFeature.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)