mainClassName org.liquibase.gradle.OutputEnablingLiquibaseRunner does not work on liquibase 3.7.0 about liquibase-gradle-plugin HOT 5 CLOSED

Thanks for raising this issue. It looks like Liquibase 3.7.0 broke logging again (among other things). I'll look into it.

from liquibase-gradle-plugin.

The underlying problem here is CORE-3220. The OutputEnablingLiquibaseRunner was created as an ugly hack to workaround CORE-3220, but that hack no longer works with the changes to Liquibase Logging.

Ultimately, this needs to be fixed in Liquibase itself. I've proposed a solution (or at least the start of one) in the Jira, I'm just waiting to see if the core team likes the idea. If they do, this should fix the problem. I wouldn't even need a new release of the plugin :-)

from liquibase-gradle-plugin.

I've submitted a Pull Request to address this issue. All we need now is for it to be merged into Liquibase, and a new version to be released.

from liquibase-gradle-plugin.

3.8.1 release says "Bugfixes in logging and outputFile" but pull request is not merged. But does it helps us?

from liquibase-gradle-plugin.

It does look like Logging now works. I think it shows WAY too much output for "info" mode, but at least now we get output, and we can tweak the amount of output with the logLevel argument.

At this point, I think logging issues are now squarely in the realm of Liquibase itself, so I think we should go ahead and close this issue.

from liquibase-gradle-plugin.