Add possibility to use extensions such as liquibase-hibernate5 about liquibase-gradle-plugin HOT 3 CLOSED

I must confess that I've never used liquibase plugins...

What happens when you add classpath org.liquibase.ext:liquibase-hibernate5:3.6 to your buildscript dependencies?

from liquibase-gradle-plugin.

Since my last comment, the way we handle the classpath when we run Liquibase has changed. Starting with version 2.0 of the plugin, you can useliquibaseRuntime dependencies to add artifacts to the classpath when Liquibase runs, and this has been tested with projects that use the exact liquibase-hibernate dependency you are trying to use.

Does that solve your issue?

from liquibase-gradle-plugin.

Adding liquibaseRuntime 'org.liquibase.ext:liquibase-hibernate5:3.6' works like charm. Before 2.0 using classpath also worked fine. In fact, using liquibaseRuntime seems to let you take full advantage of io.spring.gradle:dependency-management-plugin

I also had to add liquibaseRuntime sourceSets.main.output to avoid this issue: liquibase/liquibase-hibernate#170

from liquibase-gradle-plugin.