-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot fingerprint input property #120
Comments
Hi, |
Ran into the same issue with 2.2.0 today. Any updates on this? |
Hi,
Environment:
plugins {
id "java"
id "org.springframework.boot" version "3.1.6"
id "io.spring.dependency-management" version "1.1.4"
id 'org.liquibase.gradle' version '2.2.1'
id 'org.graalvm.buildtools.native' version '0.9.28'
}
... However, if I remove the org.graalvm.buildtools.native plugin, everything works fine. |
I encounter the same problem as gustabart with slightly different versions: id 'org.springframework.boot' version '3.2.0' |
any workaround till the time the issue is fixed? |
While I can confirm this fixes the issue, I cannot add a test since there is no infrastructure to execute the tasks. ref: liquibase#120
While I can confirm this fixes the issue, I cannot add a test since there is no infrastructure to execute the tasks. ref: liquibase#120
While I can confirm this fixes the issue, I cannot add a test since there is no infrastructure to execute the tasks. ref: liquibase#120
While I can confirm this fixes the issue, I cannot add a test since there is no infrastructure to execute the tasks. ref: liquibase#120
A fix for this would be great, since the liquibase task forces any task downstream of it to run every time. Also, it may be that the new and shiny version using liquibase 4.28.0 - if it avoids this issue - will introduce new issues that will take some time to iron out. |
At long last, version 3.0.0 of the plugin has been released. The LiquibaseCommand class is no longer part of the plugin, so is this sitll an issue? |
@stevesaliman I'm still getting this error. Here some chunks from the
Many thanks! Any hint is appreciated! |
@pareekdevanshu @treethingy @gustabart If you are using GraalVM gradle plugin, you can set these in your
The reason why GraalVM gradle plugin destorys liquibase tasks, is that: -> GraalVM gradle plugin tries to instrument every task |
I am running into this issue in version 3.0.1 of this plugin when I set an output on the task in order to make an incremental build: tasks.update.configure {
outputs.dir("PATH_WITH_MY_CHANGELOG")
} I then receive the following error:
When looking in the source, I saw that |
When using Gradle 8.1, and running any liquibase command im getting this error:
The text was updated successfully, but these errors were encountered: