Re: Problems with logging to karaf.log from liquibase >3
Hi Depending of the Karaf version, you can use either spifly or loader directly. Regards JB Le lun. 6 juin 2022 à 22:20, Steinar Bang a écrit : > > Steinar Bang : > > > The project now has an integration test, and the karaf.log of the > > integration test shows liquibase output, for version 3.8.0 of liquibase, > > so I can use this to debug liquibase logging for 4.x versions: > > > https://github.com/steinarb/liquibase-karaf-feature/tree/master/liquibase-integration-test/karaf.liquibase.tests > > So I've tried the newest liquibase release: 4.11.0 > > Version 4.11.0 failed because the MANIFEST.MF was missing OSGi headers. > I've filed an issue for the missing headers: > https://github.com/liquibase/liquibase/issues/2922 > > Version 4.10.0 has OSGi headers in the MANIFEST.MF. > > But version 4.10.0 fails because it can't find > osgi.serviceloader.registrar: > > testLoadFeature(no.priv.bang.karaf.liquibase.tests.LiquibaseKarafFeatureIntegrationTest): > Unable to resolve org.liquibase.core/4.10.0: missing requirement > [org.liquibase.core/4.10.0] osgi.extender; > filter:="(osgi.extender=osgi.serviceloader.registrar)" > > I've googled and osgi.serviceloader.registrar seems to be part of > something called the OSGi service loader mediator: > https://stackoverflow.com/a/43781701 > > Is the OSGi service loader mediator easily available in karaf? > I.e. loadable by a feature? > > > >
Re: Deployment inside a Apache Karaf docker container with deploy folder doesn't work
Hi Thanks, I will take a look as I’m preparing releases right now. Regards JB Le lun. 6 juin 2022 à 18:10, Gerald Kallas a écrit : > Hi JB, all, > > I did perform all necessary steps to reproduce the issue, see the JIRA > ticket here > > https://issues.apache.org/jira/browse/KARAF-7448 > > So no volumes at the moment, that's the further steps to referece the > deploy and etc folders outside the container. Tested this as well, doesn't > even work. > > Hope you might find a solution soon, as in older versions of Karaf it > worked as expected. > > Best > Gerald > > > Jean-Baptiste Onofré hat am 04.06.2022 06:46 > geschrieben: > > > > > > Hi Gerald > > > > which docker image are you using ? Do you have anything special about > volume ? > > Does bundle:install work (I'm pretty sure it works as I'm using it ;)) ? > > > > Regards > > JB > > > > On Fri, Jun 3, 2022 at 4:24 PM Gerald Kallas > wrote: > > > > > > Hi folks. > > > > > > I did create a vanilla docker container based on Apache Karaf, Pax Web > Jetty and Apache Camel. > > > > > > The deployment of artefacts inside the deploy folder doesn't work > inside the docker container. With the base installation on Linux it works > properly. Any hints where I might start research the cause for that, e.g. > which configuration, log hints etc? > > > > > > Best > > > Gerald >
Re: Problems with logging to karaf.log from liquibase >3
> Steinar Bang : > The project now has an integration test, and the karaf.log of the > integration test shows liquibase output, for version 3.8.0 of liquibase, > so I can use this to debug liquibase logging for 4.x versions: > > https://github.com/steinarb/liquibase-karaf-feature/tree/master/liquibase-integration-test/karaf.liquibase.tests So I've tried the newest liquibase release: 4.11.0 Version 4.11.0 failed because the MANIFEST.MF was missing OSGi headers. I've filed an issue for the missing headers: https://github.com/liquibase/liquibase/issues/2922 Version 4.10.0 has OSGi headers in the MANIFEST.MF. But version 4.10.0 fails because it can't find osgi.serviceloader.registrar: testLoadFeature(no.priv.bang.karaf.liquibase.tests.LiquibaseKarafFeatureIntegrationTest): Unable to resolve org.liquibase.core/4.10.0: missing requirement [org.liquibase.core/4.10.0] osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)" I've googled and osgi.serviceloader.registrar seems to be part of something called the OSGi service loader mediator: https://stackoverflow.com/a/43781701 Is the OSGi service loader mediator easily available in karaf? I.e. loadable by a feature?
