Maven update

update deploys any changes that are in the changelog file and that have not been deployed to your database yet.


update is typically used to apply database changes that are specified in the changelog file to your database.

When you run the update goal, Liquibase sequentially reads changesets in the changelog file, then it compares the unique identifiers of id, author, and path to filename to the values stored in the DATABASECHANGELOG table.

  • If the unique identifiers do not exist, Liquibase will apply the changeset to the database.
  • If the unique identifiers exist, the MD5Sum of the changeset is compared to the one in the database.
  • If they are different, Liquibase will produce an error message that someone has changed it unexpectedly. However, if the status of the runOnChange or runAlways changeset attribute is set to TRUE, Liquibase will re-apply the changeset.

Maven configuration

You can configure Liquibase Maven in multiple ways. You can pass arguments like <changeLogFile> in Maven directly in your pom.xml file, in a file referenced in your POM, as environment variables, or as JVM system properties.

Tip: For more information about the Maven configuration, see Configuring Maven.

Running the update Maven goal

Running the update goal requires a Maven project to be implemented.

To run the goal, type the following in your command prompt:

mvn liquibase:update

update optional Maven configuration attributes

Attribute Definition

Specifies the path to the directory where Liquibase can find your changelog file.


The changelog file for Liquibase to use.


Specifies the catalog Liquibase will use to create your changelog tables.


Specifies the schema Liquibase will use to create your changelog tables.


Int. Specifies the number of changes to apply to the database. If 0, all changes not already applied to the database are applied. Default value is: 0.


Boolean. Forces checksums to be cleared from the DATABASECHANGELOG table. Default value is: false.


Specifies which contexts Liquibase will execute, which can be separated by a comma if multiple contexts are required. If a context is not specified, then all contexts will be executed.


Specifies the table name to use for the DATABASECHANGELOGLOCK table.


Specifies the table name to use for the DATABASECHANGELOG table.


Specifies the database object class.


Specifies the default catalog name to use for the database connection.


Specifies the default schema name to use for the database connection.


Specifies the driver class name to use for the database connection.


Specifies the location of a JDBC connection properties file which contains properties the driver will use.


Boolean. Specifies whether to perform a drop on the database before executing the change. Default value is false.


Deprecated. Boolean. Use an empty or null value for the password instead. Default value is: false.


Specifies a map-based collection of changelog properties to apply.


Specifies a property-based collection of changelog properties to apply.


Boolean. Includes a Maven project artifact in the class loader, which obtains the Liquibase properties file and changelog files. Default value is true.


Boolean. Includes the Maven test output directory in the class loader which obtains the Liquibase properties file and changelog files. Default value is true.


Specifies which labels Liquibase runs, and which can be separated by a comma if multiple labels are required or you need to designate a more complex expression. If no label is specified, then all labels are run.


Specifies your Liquibase Pro license key.


Boolean. Specifies whether to ignore the catalog or database name. Default value is: false.


Boolean. Specifies whether to ignore the schema name. Default value is: false.


Indicates that you want to set the character encoding of the output file during the updateSQL phase.


Specifies the database password for the database connection.


Deprecated. Boolean. Controls whether users are prompted before executing changesets to a non-local database. Default value is: true.


Specifies the Liquibase properties file to use for configuration, like


Boolean. Indicates that you want the file to override any settings provided in the Maven plugin configuration. By default, if a property is explicitly specified, it is not overridden if it also appears in the properties file. Default value is: false.


Specifies the property provider, which must be a java.util.Properties implementation.


Specifies the server ID in the Maven settings.xml to use when authenticating.

Available in Liquibase 4.24.0+


Produces a summary list of any changesets skipped and why they were skipped. Valid values are OFF, SUMMARY, and VERBOSE. Default: SUMMARY. Available in Liquibase 4.24.0+.

Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.

Available in Liquibase 4.24.0+


Summary output to report update summary results. Valid values are LOG, CONSOLE, and ALL. If set to LOG, the --show-summary output is sent to the file specified in --log-file. If set to CONSOLE, the --show-summary output is sent to STDOUT. If set to ALL, the --show-summary output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.


Boolean. Specifies whether to skip running Liquibase. The use of this attribute is not recommended but can be used when needed. Default value is: false.


Specifies a list of system properties you want to pass to the database.


Apply changes up to and including the changesets with the given tag goal.


Specifies the database URL you want to use to execute Liquibase.


Specifies the database username for the database connection.


Boolean. Controls the amount of output detail when you call the plugin. Default value is: false.