The package pulls liquibase-commercial in?

[veda-tschoening]

I've update from 4.26.0 to 4.27.0 and are able to reliable reproduce that this package pulls liquibase-commercial in now. That's breaks things at runtime for me, because it bundles Jackson in a version newer than the one I'm using, is needed by my outdated Spring app etc. I get all kinds of different error like NoSuchFieldError, MethodNotFoundException etc. because of the incompatibilities. Though, things heavily depend on the unpredictable order of the JARs in the classpath, under some environment things work without any error, under other they break instantly.

Switching between 4.26.0 and 4.27.0 reliably changes the following lines for me:

ths@LAP3738 MINGW64 ~/IdeaProjects/app-mediator (main)
$ mvn dependency:tree
[...]
[INFO] +- org.liquibase.ext:liquibase-db2i:jar:4.27.0:compile
[INFO] |  \- org.liquibase:liquibase-commercial:jar:4.27.0:compile

Do you have any explanation for this behaviour?

Thanks!

[SvenT23]

From what I can tell this is because of the new setup with the liquibase-parent.
This also now specifies the liquibase commercial EULA as the license for this project when using it, instead of the Apache 2.0 license specified in the readme.

The commercial dependency seems to have been changed (back) to scope provided in 0.3.9 but version 4.27.0 uses 0.3.7:
liquibase/liquibase-parent-pom@26666ac