Allow extending classpath in gradle task config #1738
this adds a testcase to show, that flyway migration fails for java migrations when they use classes coming from a custom gradle configuration
this adds a property 'classpathExtension' that allows a user to extend the classpath flyway uses to run its tasks and especially its java migrations.
# Conflicts: # flyway-gradle-plugin-largetest/src/test/java/org/flywaydb/gradle/largetest/GradleLargeTest.java # flyway-gradle-plugin/src/main/java/org/flywaydb/gradle/FlywayExtension.java # flyway-gradle-plugin/src/main/java/org/flywaydb/gradle/task/AbstractFlywayTask.java
@simschla Thanks. I assume it has passed your manual tests.
Could you also provide a pull request with a usage example for https://github.com/flyway/flywaydb.org/blob/flyway-5.1.0/documentation/gradle/index.md (flyway-5.1.0 branch)? This should most likely be a new ### section following https://flywaydb.org/documentation/gradle/#build-script-multiple-databases