Maven futureRollbackSQL

futureRollbackSQL is a helper goal that produces the raw SQL Liquibase would need to roll back changes that have not yet been deployed to your database.


futureRollbackSQL is typically used when you want to inspect the raw SQL Liquibase would use to revert changes associated with undeployed changesets. The futureRollbackSQL goal generates the SQL that is required to roll back the database to the current state after the next update.

It is best practice to inspect SQL Liquibase would run when using the update goal so you can review any changes the command would make to your database.

Note: The updateSQL goal is also a helper goal that you can use before running the update goal. The main difference is that updateSQL creates objects associated with undeployed changesets and futureRollbackSQL drops objects associated with undeployed changesets.

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.

Before running the futureRollbackSQL goal, add <outputChangeLogFile>yourOutputFileName.txt</outputChangeLogFile> to pom.xml or set it in one of the other ways specified.

Running the futureRollbackSQL Maven goal

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

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

mvn liquibase:futureRollbackSQL

futureRollbackSQL 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.


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.


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.


Specifies the file to output the rollback/migration SQL script to. If it exists, it will be overwritten. Default value is: ${}/liquibase/migrate.sql.


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.


Defines the number of changesets to roll back. Default value is: 1.


Defines the date for which you want to roll back the database. The format of the date must match either an ISO date format or that of the DateFormat.getDateInstance() for the platform the plugin is being executed on.


Defines the tag for which you want to roll back the database.


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


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.


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.