Add support for org.flywaydb:flyway-core:10.0.0

[wetted]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The graalvm-reachability-metadata supports org.flywaydb 9.0.1, but is broken for flyway 10.0.0
/~https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/org.flywaydb/flyway-core

Describe the solution you'd like
A clear and concise description of what you want to happen.

• add support for org.flywaydb:flyway-core:10.0.0
• add support for org.flywaydb:flyway-sqlserver:10.0.0
• add support for org.flywaydb:flyway-database-oracle:10.0.0
• add support for org.flywaydb:flyway-database-postgresql:10.0.0

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

• null

Additional context
Add any other context or screenshots about the feature request here.

  | Caused by: org.graalvm.nativeimage.MissingReflectionRegistrationError: The program tried to reflectively invoke method public java.lang.String org.flywaydb.core.internal.command.clean.CleanModeConfigurationExtension.getNamespace() without it being registered for runtime reflection. Add public java.lang.String org.flywaydb.core.internal.command.clean.CleanModeConfigurationExtension.getNamespace() to the reflection metadata to solve this problem. See https://www.graalvm.org/latest/reference-manual/native-image/metadata/#reflection for help. |  
/~https://github.com/micronaut-projects/micronaut-flyway/actions/runs/6935025730/job/18864351069?pr=472

[mhalbritter]

Flyway fails with Spring Boot 3.4.0-M2 which uses Flyway 10.17.1:

Caused by: org.graalvm.nativeimage.MissingReflectionRegistrationError: The program tried to reflectively invoke method public boolean org.flywaydb.core.internal.publishing.PublishingConfigurationExtension.isPublishResult() without it being registered for runtime reflection. Add public boolean org.flywaydb.core.internal.publishing.PublishingConfigurationExtension.isPublishResult() to the reflection metadata to solve this problem. See https://www.graalvm.org/latest/reference-manual/native-image/metadata/#reflection for help.
at org.graalvm.nativeimage.builder/com.oracle.svm.core.reflect.MissingReflectionRegistrationUtils.forQueriedOnlyExecutable(MissingReflectionRegistrationUtils.java:72)
at java.base@21.0.3/java.lang.reflect.Method.acquireMethodAccessor(Method.java:77)

[mhalbritter]

I've added metadata for Flyway 10.17.1 in #531.

[asm0dey]

With 10.20.1 and spring 3.4.0 it fails with

The program tried to reflectively invoke method

   public java.lang.String org.flywaydb.core.internal.configuration.extensions.DeployScriptFilenameConfigurationExtension.getScriptFilename()

 without it being registered for runtime reflection.

[mhalbritter]

This can be fixed by using the latest version of the reachability metadata:

graalvmNative {
	metadataRepository {
		version = '0.3.15'
	}
}

or

<plugin>
	<groupId>org.graalvm.buildtools</groupId>
	<artifactId>native-maven-plugin</artifactId>
	<configuration>
		<metadataRepository>
			<version>0.3.15</version>
		</metadataRepository>
	</configuration>
</plugin>

[msosa]

Upgrading to Spring Boot 3.4.1 did not seem to fix it for me. The location of my error seems a little different than the others I see here though:

Caused by: org.graalvm.nativeimage.MissingReflectionRegistrationError: The program tried to reflectively invoke method public boolean org.flywaydb.core.internal.publishing.PublishingConfigurationExtension.isCheckDriftOnMigrate() without it being registered for runtime reflection.

[mhalbritter]

Spring Boot 3.4.1 will use the latest Native Build Tools release, which includes this reachability metadata version by default.

This isn't true, sorry!

Spring Boot 3.4.1 uses Native Build Tools 0.10.4, which uses the 0.3.14 metadata.

So the workaround from #424 (comment) still applies to Spring Boot 3.4.1.

[goafabric]

I am having the same problem since boot 3.4x with PublishingConfigurationExtension,
and also since 3.3 there is a similar problem with "TransactionalModel" if flyway is combined with Hibernate.

The following Spring annotations would fix it, i think this could be easily translated to graalvm defaults.
And I understand the workaround that Moritz mentioned concerning the first issue.

@RegisterReflection(classes = {org.flywaydb.core.internal.publishing.PublishingConfigurationExtension.class, org.flywaydb.database.postgresql.TransactionalModel.class}, memberCategories = {MemberCategory.INVOKE_PUBLIC_METHODS, MemberCategory.INVOKE_PUBLIC_CONSTRUCTORS})