Liquibase doesn't respect logging configuration

[php-coder]

This issue is the same as #3470: liquibase doesn't use logging configuration -- it prints INFO messages when I want to see only warnings and its messages have a different format.

Steps to reproduce

$ git clone https://github.com/php-coder/mystamps.git
$ cd mystamps
$ git checkout b2f1c612d9eba7a957edc602c3431de848fd55e1
$ mvn clean spring-boot:run

Observable behavior

...
[2016-08-21 12:36:50.686] boot - 3174  INFO [main] --- RequestMappingHandlerAdapter: Looking for @ControllerAdvice: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@63dde5e5: startup date [Mon Aug 21 12:36:46 CEST 2016]; root of context hierarchy
INFO 8/21/16 12:36 PM: liquibase: Successfully acquired change log lock
INFO 8/21/16 12:36 PM: liquibase: Creating database history table with name: PUBLIC.DATABASECHANGELOG
INFO 8/21/16 12:36 PM: liquibase: Reading from PUBLIC.DATABASECHANGELOG
...
INFO 8/21/16 12:36 PM: liquibase: Successfully released change log lock
[2016-08-21 12:36:53.115] boot - 3174  INFO [main] --- application: Initializing Spring FrameworkServlet 'dispatcherServlet'
...

Expected behavior

I shouldn't see all of these messages from Liquibase because I'm interesting only in warnings:

$ grep liquibase src/main/resources/application-test.properties
liquibase.contexts: scheme, init-data, test-data
liquibase.change-log: classpath:/liquibase/changelog.xml
logging.level.liquibase: WARN

Workaround

Also I found out that it was working in Spring Boot 1.3.0.RELEASE but broken since 1.3.1.RELEASE. To test it you can downgrade the version and test that it works:

sed -i 's|1.3.7.RELEASE|1.3.0.RELEASE|;s|9.2.18.v20160721|9.2.11.v20150529|' pom.xml

Let me know if you need more information.

[wilkinsona]

Interestingly, it does respect the logging configuration when run using java -jar

[wilkinsona]

It works with an executable archive as it prevents Liquibase from loading its logger implementation until we've installed our SpringPackageScanClassResolver at which point our custom logger is used instead.

[wilkinsona]

We need to reinstate the workaround from this commit and add a test to ensure that it doesn't get broken again.

[php-coder]

@wilkinsona Thank you for the fast feedback and the fix!

Will it be fixed in 1.4.x or this version doesn't need it?

[wilkinsona]

The fix is in 1.3.x and master (1.4.x).

[prerakalw]

Refer https://github.com/prerakalw/liquibase-with-logs

[snicoll]

@prerakalw thanks for sharing but this issue has been fixed over 2 years ago and both Spring Boot 1.3 and 1.4 are EOLed by now. Please upgrade.

[prerakalw]

@snicoll i was using liquibase 3.6.2 binary for database change sets deployment, and during deployment it does not logs anything. Sorry but can you please elaborate where should i upgrade spring boot.