Make Gradle 3.0 the new minimum supported version #1429
Closed
Milestone
Comments
From the same issue posted on the Gradle forums, it appears the solution may be to simply release another version using Gradle 3 to clear up the bytecode incompatibiility: |
axelfontaine
added a commit
to flyway/flywaydb.org
that referenced
this issue
Nov 30, 2017
We have now bumped the minimum supported Gradle version to 3.0 as part of the Flyway 5.0 release. |
axelfontaine
added a commit
to flyway/flywaydb.org
that referenced
this issue
Nov 30, 2017
dohrayme
pushed a commit
to dohrayme/flyway
that referenced
this issue
Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Flyway are you using?
4.0.3 (also tried 4.0.2)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
Gradle plugin
What database are you using (type & version)?
MySQL 5.6.27
What operating system are you using?
MacOS X
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Created a custom Gradle task in the buildSrc directory that extends AbstractFlywayTask with Gradle 3.0. (Works fine in Gradle 2.13). I created a sample project to duplicate the issue, which can be found here: Gradle 3.0/FlywayDB 4.0.3 Issue
Ran the command:
./gradlew build
What did you expect to see?
Expected to be able to perform a Gradle build, including database migrations.
What did you see instead?
The build fails with an exception:
The text was updated successfully, but these errors were encountered: