Picocli dependency is not published as optional dependency of liquibase-core

[mr-serjey]

Search first

• I searched and no similar issues were found

Description

Despite the fact that liquibase-core incorporates liquibase-cli in a shaded jar, it doesn't export liquibase-cli's dependency called picocli as optional. So the version of picocli that works with a particular version of liquibase-core is vanishes in published liquibase-core artifact. This makes hard to use CLI integration (liquibase.integration.commandline package of liquibase-core) in libraries and/or plugins.

Given the fact that exporting picocli dependency as part of liquibase-core has been already considered...

It would be nice if it come through as an optional dependency, but maven doesn't easily do that...
see:https://github.com/liquibase/liquibase/blob/master/liquibase-core/pom.xml#L45

This can be done to remediate the problem and will help to unblock at least liquibase-gradle-plugin project...

• liquibase-gradle-plugin should declare picocli as a transitive dependency liquibase-gradle-plugin#129

Steps To Reproduce

1. Create application project with liquibase-core dependency (maven/gradle)
2. Add LiquibaseLauncher.main(cliArgs) into the application routine
3. Run the application

Error: class def not found

Expected/Desired Behavior

1. Create application project with liquibase-core dependency (maven/gradle)
2. Add LiquibaseLauncher.main(cliArgs) into the application routine
3. Run the application

No error expected

Liquibase Version

4.+

Database Vendor & Version

No response

Liquibase Integration

cli

Liquibase Extensions

No response

OS and/or Infrastructure Type/Provider

No response

Additional Context

No response

Are you willing to submit a PR?

• I'm willing to submit a PR (Thank you!)

[filipelautert]

Hello @mr-serjey - I believe optional is fine. I created PR #5042 to implement this change.

[mr-serjey]

Great job @filipelautert!