Modify Liquibase Gradle Plugin to handle custom Liquibase extensions

[mikelee3]

We've developed a Liquibase extension that implements a new Liquibase command, but the Gradle plugin does not seem to pick it up and we cannot call it using this plugin. The extension runs correctly if we install it directly into the Liquibase command line application, so we know it works in the general sense.

Could the Liquibase Gradle plugin be modified to handle this type of change?

[stevesaliman]

The next release of the Gradle plugin is being redesigned to work with Liquibase's new Command API, so if your extension registers with it, it should work with it.

Unfortunately, the Command API has a bug in it which prevents me from finishing the work on this effort. I'm hoping it will be fixed in version 4.28.

[mikelee3]

Thanks, looking forward to the update.

[lfgcampos]

@stevesaliman 4.28.0 was released 2 days ago

any updates on this?

also, would the new redesign to work with Liquibase's new Command API fix other issues like this? https://github.com/liquibase/liquibase-gradle-plugin/issues/119

they feel somehow connected 🤔

[stevesaliman]

Unfortunately, there is still a bug when trying to use changelog parameters with the command API. I'm trying to get feedback from the Liquibase team on how to best resolve it.

[stevesaliman]

At long last, version 3.0.0 has now been released to production. Do things now work as expected?

[stevesaliman]

Closing for inactivity.