Re : Unable to replace logger, ServiceLocator.instance() returns null

What I did to fix this, was to ensure that the getPriority() method of my logger returned a high number:

2. package liquibase.ext.logging;
3. 
   
4. import liquibase.logging.core.AbstractLogger;
5. 
   
6. public class UkelonnLiquibaseLogger extends AbstractLogger {
7.     ...
9.     /**
10.      * The value returned here will determine if liquibase is to use this logger.
11.      * If the value is too low, liquibase will use the default logger.
12.      */
13.     @Override
14.     public int getPriority() {
15.         return Integer.MAX_VALUE;
16.     }
17. }

When debugging I found that the ServiceLocator.getInstance() method eventually returned something other than null, and a logger was attempted created. However, since the getPriority() method returned 0, the default logger was picked instead.

Now this works for me in the unit tests.

However, in the OSGi context liquibase still logs to the console. This happens both in the karaf-based pax exam tests, and in apache karaf itself.

I have exported the liquibase.ext.logger package from the OSGi bundle the UkelonnLiquibaseLogger is implemented in.

FYI The reason I picked ClassLoaderResourceAccessor over the OSGiResourceAccessor, was that I couldn't figure out how to make the OSGiResourceAccessor work in the unit tests, and the ClassLoaderResourceAccessor with the class loader set explicitly, finds the database changeset files both when running in unit tests and when running in OSGi.