preserve-classpath-prefix-in-normalized-paths

Uses

Liquibase uses the Java Virtual Machine (JVM) to resolve resource paths like your classpath, which is a list of file paths where changelogs, configuration files, and JAR files (bundles of Java classes) are stored. The JVM uses the classpath to search for, load into memory, and link each of those resources to prepare them for use in Liquibase.

Liquibase lets you set the classpath using the global parameter --classpath. Liquibase normalizes the classpath value you specify by converting it to a consistent format. By default, if your classpath contains the prefix classpath:, Liquibase removes the prefix. Then Liquibase sends the normalized classpath to the ResourceAccessor.

However, you may be trying to implement a custom ResourceAccessor that needs to accept an abstract URL as the Liquibase classpath. For example, you may want to specify a root resource path containing a nested (hierarchical) classpath as the value of --classpath instead of a relative or absolute path directly connected to the file system. If Liquibase strips the classpath: protocol, your custom class cannot access the correct sub-resource locations.

If you want to preserve the classpath: prefix in your Liquibase resource path, set --preserve-classpath-prefix-in-normalized-paths to true. This way, Liquibase path normalization does not strip classpath: from the resource path it sends to the ResourceAccessor.

Syntax

You can set this parameter in the following ways:

For more information, see Working with command parameters