stevesaliman
commented
2 years ago the problem seems to be with line 186: classpath.allDependencies appears to only tell me the version that was declared, not the version that will actually be used, which is ultimately what the plugin needs to know to choose the correct class to use for processing arguments.
The gradlew dependencies command shows the correct version, so I'll need to figure out how to get my plugin task to get that same information.
esselesse
Hi 👋
After we upgraded the Liquibase Gradle plugin to version
2.1.0, theupdatetask started failing witheven though nothing else in the build file changed (which means we very much still do have
liquibase-corein theliquibaseRuntimeconfiguration). However, as we also use the Spring dependency management plugin we have it configured like so:letting said plugin choose the right version for us.
After examining the the sources I found out this is the root cause the issue: this check always fails in our case as we simply don't have an explicit version stated in the dependency notation.
A workaround is to add the explicit version, but that goes against the spirit of the dependency management plugin (and possibly any other kind of custom dependency management scheme).