spring/spring-boot
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-boot.git synced 2026-09-17 12:09:16 +00:00
Code Issues Projects Releases Wiki Activity

Adapt documentation for Liquibase and Flyway to new modules

Browse Source 
See gh-49839

Signed-off-by: Piotr Papaj <4591951+ppapaj@users.noreply.github.com>
This commit is contained in:
Piotr Papaj
2026-04-03 09:10:39 +02:00
committed by Stéphane Nicoll
parent b2aa314f42
commit ebe074c7d3
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-initialization.adoc
+4 -4
View File
@@ -98,8 +98,8 @@ Spring Boot supports two higher-level migration tools: https://flywaydb.org/[Fly
=== Execute Flyway Database Migrations on Startup
To automatically run Flyway database migrations on startup, add the appropriate Flyway module to your classpath.
In-memory and file-based databases are supported by `org.flywaydb:flyway-core`.
Otherwise, a database-specific module is required.
In-memory and file-based databases are supported by `spring-boot-starter-flyway`.
Otherwise, a database-specific module is also required.
For example, use `org.flywaydb:flyway-database-postgresql` with PostgreSQL and `org.flywaydb:flyway-mysql` with MySQL.
See https://documentation.red-gate.com/fd/supported-databases-and-versions-143754067.html[the Flyway Documentation] for further details.
@@ -169,11 +169,11 @@ With that setup, migrations in `dev/db/migration` run only when the `dev` profil
[[howto.data-initialization.migration-tool.liquibase]]
=== Execute Liquibase Database Migrations on Startup
To automatically run Liquibase database migrations on startup, add the `org.liquibase:liquibase-core` to your classpath.
To automatically run Liquibase database migrations on startup, add the `spring-boot-starter-liquibase` to your classpath.
[NOTE]
====
When you add the `org.liquibase:liquibase-core` to your classpath, database migrations run by default for both during application startup and before your tests run.
When you add the `spring-boot-starter-liquibase` to your classpath, database migrations run by default for both during application startup and before your tests run.
This behavior can be customized by using the configprop:spring.liquibase.enabled[] property, setting different values in the `main` and `test` configurations.
It is not possible to use two different ways to initialize the database (for example Liquibase for application startup, JPA for test runs).
====