Introducing Agent Safe Governance for the AI Era

Liquibase starters for Maven

Last updated: January 8, 2026

Liquibase starters for Maven are preconfigured Maven artifacts that bundle Liquibase dependencies and configuration to help you quickly set up Liquibase in a Maven-based project. Rather than manually maintaining a list of individual dependencies and configuring the Liquibase Maven plugin from scratch in your pom.xml file, you can add a single Liquibase starter dependency to include everything you need for a specific Liquibase version automatically. This convenience package simplifies initial setup, ensures compatible dependency versions, and reduces configuration overhead and potential version conflicts. Once the maven starters are installed, you will be able to use the following Liquibase extensions in Maven. These are the two Liquibase starters:

  • liquibase-secure-starter - contains the core commercial engine

    • com.liquibase:liquibase-commercial

  • liquibase-secure-starter-all - contains extensions with their database drivers embedded directly into each extension artifact (shaded), so you don't need to manage driver dependencies separately

    • com.liquibase : liquibase-commercial

    • com.liquibase.ext : liquibase-commercial-bigquery

    • com.liquibase.ext : liquibase-commercial-mongodb

    • com.liquibase.ext : liquibase-commercial-databricks

    • com.liquibase.ext : liquibase-commercial-snowflake

    • com.liquibase.ext : liquibase-commercial-couchbase

    • com.liquibase.ext : liquibase-aws-extension

    • com.liquibase.ext.vaults : liquibase-hashicorp-vault

    • com.liquibase.ext : liquibase-azure

Uses

Use liquibase-secure-starter if you're connecting to one of the core supported databases — such as PostgreSQL, MySQL, Oracle, or SQL Server. It pulls in the commercial Liquibase engine and nothing else, keeping your dependency footprint small.

Use liquibase-secure-starter-all if you need any of the bundled extensions — BigQuery, MongoDB, Databricks, Snowflake, Couchbase, AWS, Azure, or HashiCorp Vault. Each extension comes with its database driver already embedded, so you don't need to manage those dependencies separately.

Before you begin

  • Ensure Liquibase Secure 5.1+ is installed on your machine

  • Ensure Maven is installed on your machine

  • Ensure you have your Liquibase Secure License key applied

  • Ensure your liquibase.properties file is configured

Procedure

1

Open your pom.xml file

This file defines your project's dependencies and plugins.

2

Add this code to your pom file

loading
3

Run the Maven goal in your terminal to verify the installation was successful

mvn liquibase:status

Results

Notice in your CLI log the version of Liquibase: 5.2.0

Example CLI output:

[INFO] Scanning for projects... [INFO] [INFO] -------------------< com.example:liquibase-project >-------------------- [INFO] Building Liquibase Secure Project 1.0 [INFO] from pom.xml [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- liquibase:5.2.0:status (default-cli) @ liquibase-project --- [INFO] ------------------------------------------------------------------------