[
https://issues.apache.org/jira/browse/KARAF-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860705#comment-17860705
]
ASF subversion and git services commented on KARAF-7843:
--------------------------------------------------------
Commit b96d2cc02c233e7cabd6244ba3451410e0eda522 in karaf's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b96d2cc02c ]
Merge pull request #1852 from steinarb/change-spifly-start-level-to-20
Make spifly feature start spifly.dynamic.bundle at start-level 20 to fix
KARAF-7843
> It would be nice if the spifly feature was on a start-level other than the
> default
> ----------------------------------------------------------------------------------
>
> Key: KARAF-7843
> URL: https://issues.apache.org/jira/browse/KARAF-7843
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Reporter: Steinar Bang
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.5.0, 4.4.7
>
>
> [Apache Aries SPI
> Fly|https://aries.apache.org/documentation/modules/spi-fly.html] helps
> translating SPI services into OSGi services.
> SPI Fly looks for <Require-Capability> OSGi manifest headers and then tries
> to satisfy them with services found by scanning for <Provide-Capability>
> headers.
> The Liquibase database migration tool is built around SPI services.
> As an OSGi bundle it utilizes SPI Fly to spin up its SPI services by adding
> both a [<Provide-Capability> for the
> services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L252]
> as well as a [<Require-Capability> for the same
> services|https://github.com/liquibase/liquibase/blob/master/liquibase-standard/pom.xml#L217]
> in the liquibase-core manifest file.
> But all of the SPI services of liquibase needs to be running before liquibase
> is actually used and there is no way to know that all the required services
> have been started.
> So to make liquibase available on the default start level 80 (where e.g.
> jdbc-config is running), liquibase and SPI Fly both has to be started on a
> lower start level (e.g. 40).
> And the built-in spifly feature of karaf starts SPI Fly on start level 80
> which is much too late for liquibase to make use of it (all SPI services will
> be started, but much too late).
> So it would be good to have the spifly feature start the spifly bundle at a
> lower start level than the default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
