I prepared some fixes for liquibase 3.7 but there was an another osgi related error. So maybe you can check liquibase 4.8.1 when it is released
Jakub On Thu, Mar 10, 2022 at 6:23 AM Jean-Baptiste Onofré <[email protected]> wrote: > > Hi Steinar, > > I'm sorry, I never tried liquidbase in Karaf. > > JUL is supported by pax-logging, so I think your approach wrapping core and > slf4j in a bundle makes sense. > > I can try your feature to check and eventually create a bundle at SMX and > corresponding Karaf in enterprise feature. > > Regards > JB > > On Wed, Mar 9, 2022 at 9:59 PM Steinar Bang <[email protected]> wrote: >> >> I've been stuck on liquibase 3.0.8 since November 2019 (heh! Since >> before corona...!), because I've been unable to make later versions log >> to karaf.log. >> >> But now I'm getting security warnings for liquibase 3, and the only way >> out is to upgrade. >> >> Does anyone else have a working setup for a recent version of liquibase? >> >> In particular: does logging to karaf.log work? >> >> Thanks! >> >> The full story: >> >> Liquibase originally had an extra adapter for logging, that used >> reflection to scan for an adapter implementation. And that posed a >> problem when using OSGi classloader. >> >> Thanks to help from the karaf user mailing list[1], I was able to make >> an existing project[2] into a bundle fragment and attach it to my >> liquibase bundles. >> >> I improved that approach into a handwritten karaf feature and a >> repacking of [2], in[3]. >> >> And this worked find for me until I came to liquibase 3.1.1[4], and then it >> started failing for me. It failed in a funny way, because the snapshots >> I built myself worked fine, but the releases from maven central failed. >> >> I eventually traced this down to an issue caused by the releases being >> built by java8 and me running with java11[5]. >> >> I provided a PR to fix this issue[6], but that was never accepted, since >> there would be no more releases to version 3[7]. >> >> The liquibase-slf4j package[4] has an upgrade to liquibase 4. >> >> What I have tried, so far, is: >> 1. Bump liquibase to 4.x and bump the liquibase-slf4j package to a >> version supporting liquibase 4 >> 2. Bump liquibase to 4.x and drop liquibase-slf4j altogether (hoping >> the java.util.logging (that is the liquibase 4.x default) would >> automagically find its way to karaf.log >> >> But in neither case logging from liquibase appeared in karaf.log. >> >> All ideas for how to debug this further would be welcome. >> >> A ready made solution for using liquibase 4.x would be even more >> welcome! :-) >> >> Thanks again! >> >> >> - Steinar >> >> >> REFERENCES: >> [1] <https://lists.apache.org/thread/8qvjjwd40z0krfpp4h40rkd47fbbbpoc> >> [2] <https://github.com/mattbertolini/liquibase-slf4j> >> [3] <https://github.com/steinarb/liquibase-karaf-feature> >> [4] >> <https://github.com/liquibase/liquibase/releases/tag/liquibase-parent-3.1.1> >> [5] <https://github.com/liquibase/liquibase/issues/1254> >> [6] >> <https://github.com/liquibase/liquibase/issues/1254#issuecomment-699611630> >> [7] >> <https://github.com/liquibase/liquibase/issues/1254#issuecomment-985743534> >>
