Gradle plugin does not resolve
implementation-scoped artifacts, only
Which version and edition of Flyway are you using?
5.2.4 latest release
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Which database are you using (type & version)?
Which operating system are you using?
macOS High Sierra 10.13.6
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
When I run
What did you expect to see?
I expect that my project's artifact dependencies are resolved correctly in runtime.
What did you see instead?
An error related to not resolved or missing migrations.
The text was updated successfully, but these errors were encountered:
No example yet, sorry. But seems it is configurable but not enabled by default: https://github.com/flyway/flyway/blob/master/flyway-gradle-plugin/src/main/java/org/flywaydb/gradle/task/AbstractFlywayTask.java#L53 and https://flywaydb.org/documentation/gradle/#extending-the-default-classpath
I get following error:
Works if I replace
@axelfontaine I tried adding "implementation" as a configuration as described in the docs which you linked to. This does not seem to work however, I get the following error message:
Also I think that it should work out of the box with "implementation" and "api" because "compile" has been deprecated and is supposed to be replaced by "implementation" or "api" depending on the context.
@johannesloher The new set of configurations is available here: https://docs.gradle.org/current/userguide/java_plugin.html#sec:java_plugin_and_dependency_management
It's interesting that the Gradle team decided to make some of them non-resolvable. Would you like to dig into the plugin code to see how this could be fixed?
Made defaults vary based on Gradle version. New default configuration names for Gradle 4.x and newer are now