I am trying to set up Liquibase in one of our projects so that developers can use it without having to pre-install. Normally, we do this through the Maven plugin, but it does not have enough control over the log level for my particular requirements in this project.
I see that there is a Maven artifact org.liquibase:liquibase-cli, which I expect to be the jar file used by the cli without the wrapping batch and shell scripts. However, when I try to resolve that artifact, I am unable to find org.liquibase:liquibase-standard, which is one of the dependencies. This could be because my in-house replica of Maven Central is blocking it, this does sometimes happen, except I cannot find this dependency at Maven Central at all! In addition, the page linked from Maven Central (http://www.liquibase.com/liquibase-cli) doesn’t exist.
Is liquibase-cli meant to be usable? If not, why publish it? If it is, is liquibase-standard resolvable?
Obviously, I can create my own limited cli (or custom maven plugin) for the one case I need and use liquibase-core directly, but I would prefer not to have to do that.