That's weird, i'm using the liquibase-slf4j as a fragment for quite sometime and i don't have this problem. but i'm using Karaf 4.0.8, and if i'm correct karaf 4.1.x changed some stuff related to logging, could be the cause of the problem.
Well, instead using the liquibase-slf4j as a fragment you can also repackage the liquibase bundle and add to it's header the liquibase.ext.logging to his Import-Package with an optional resolver, so when you install the liquibase-slf4j as a bundle ( not a fragment ) it will work. But i'm not sure it will solve the problem. -- View this message in context: http://karaf.922171.n3.nabble.com/Experiences-with-karaf-and-liquibase-tp4050470p4050503.html Sent from the Karaf - User mailing list archive at Nabble.com.
