search

liquibase / liquibase-nochangeloglock

Disables locking logic Liquibase uses to ensure only one instance is running against a database at one time. Not recommended in general but helpful at times
11 stars 5 forks source link

disabling the extension logic IS NOT WORKING #7

Open tarekbazine opened 4 years ago

tarekbazine commented 4 years ago

Hello, I tried to set liquibase.ext.nochangeloglock.enabled=false in some of my applications profiles, BUT it did not work (ie: the lock is being ignored ).

<artifactId>spring-boot-starter-parent</artifactId>
<version>2.1.3.RELEASE</version>
...
<java.version>1.8</java.version>
...
<liquibase-maven-plugin.version>3.6.3</liquibase-maven-plugin.version>
....
<dependency>
    <groupId>org.liquibase</groupId>
    <artifactId>liquibase-core</artifactId>
</dependency>
<dependency>
    <groupId>org.liquibase</groupId>
    <artifactId>liquibase-maven-plugin</artifactId>
    <version>${liquibase-maven-plugin.version}</version>
</dependency>
<dependency>
    <groupId>org.liquibase.ext</groupId>
    <artifactId>liquibase-nochangeloglock</artifactId>
    <version>1.1</version>
</dependency>

Thanks

nvoxland commented 2 years ago

The spring boot integration is not currently able to pass along generic application settings to Liquibase.

Are you able to set it as a system property? That should accept it.

nicobte commented 2 weeks ago

Hello @nvoxland, I've been trying to use this with liquibase-cassandra without success so far. Shoud it work?