![]() Or need to rename files to change to force a reordering. Strategy in place that will insure that you will never have conflicts You do choose to use the includeAll tag, make sure you have a naming This seems like a good idea at first, it quickly runs into problems IncludeAll tag to simulate Ruby on Rails Active Migrations strategy ofĪ list of changes, one per file, that are ran in file order. While the includeAll tag has many valuable uses, its use can cause In the first link on includeAll docs there's a part about why it's not a very good practice to use it Try setting relative path to your child changeLog files as such: ![]() ![]() migrations.xml (it's a master changeLog which includes all the other changeLogs) I think it'd be a good idea to make the following structure: -src I am not able to understand your question 100% but I think below solution will do the job for you to configure multiple class paths for liquibase There just must be an easy solution to this that I just can't seem to find? Feel free to ask for more code snippets but the rest is quite straightforward according to the documentation from Liquibase with the liquibase.propterties file etc in my setup. Properties.load(new FileInputStream(propsFile))ĬhangeLogFile propertiesĪnd the Liquibase setup in application.yml is: spring:ĬhangeLog: classpath:/db/changelog-master.yml My activities in adle is like this: liquibase /src/main/resources/liquibase.properties") Would really appreciate some help to be able to use Liquibase both when starting the application and when using commands with the plugin but I can't seem to find a way around this silly thing. To work (else the file can't be found) and the path in my changelog-master file is:īut if I use plugin commands (changelogSync for example) the path needs to be from the src, like: src/main/resources/db/changelog-master.yml When running the application through settings in application.yml file the changelog needs to be: changeLog: classpath:/db/changelog-master.yml The problem then occurred when I was adding the Luquibase Gradle plugin (which also is needed for future support) because the can't find the changelog file with the same path. After a lot of struggling I got it to work when starting the application, it runs through the master changelog and the included changelogs/changesets. I'm stuck with a silly but annoying problem with implementing Liquibase to my existing project. ![]()
0 Comments
Leave a Reply. |