Fix Flyway autoconfigure

In Spring Boot 4.0, auto-configurations were extracted from the
monolithic spring-boot-autoconfigure module into separate modules.
Having flyway-core on the classpath is no longer enough — the
Flyway auto-configuration class is now in a separate module that
needs to be included in the dependencies.

Author: jannebe

development.sh

@@ -136,6 +136,9 @@ print_usage() {
   test
     Run tests locally.
 
+  run
+    Run the application locally.
+
   stop
     Stop Docker containers.
 
@@ -174,6 +177,10 @@ case $COMMAND in
     run_tests
     ;;
 
+  run)
+    mvn spring-boot:run -Pdev
+    ;;
+
   stop)
     stop_all
     ;;

pom.xml

@@ -370,8 +370,8 @@
             <artifactId>postgresql</artifactId>
         </dependency>
         <dependency>
-            <groupId>org.flywaydb</groupId>
-            <artifactId>flyway-core</artifactId>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-flyway</artifactId>
         </dependency>
         <dependency>
             <groupId>org.flywaydb</groupId>

src/test/kotlin/fi/hsl/jore4/auth/FlywayAutoConfigurationPresentTest.kt

@@ -0,0 +1,15 @@
+package fi.hsl.jore4.auth
+
+import org.junit.jupiter.api.Assertions.assertNotNull
+import org.junit.jupiter.api.Tag
+import org.junit.jupiter.api.Test
+
+@Tag("unitTest")
+class FlywayAutoConfigurationPresentTest {
+
+    @Test
+    fun `flyway auto-configuration class is on the classpath`() {
+        val clazz = Class.forName("org.springframework.boot.flyway.autoconfigure.FlywayAutoConfiguration")
+        assertNotNull(clazz, "FlywayAutoConfiguration must be on the classpath via spring-boot-starter-flyway")
+    }
+}