JHipster与Liquibase问题：liquibaseClearChecksums任务执行失败

Hey there, I’ve dealt with my fair share of Liquibase headaches in JHipster apps, so let’s walk through some fixes for your ./gradlew liquibaseClearChecksums error—even after adding the liquibase-hibernate5 dependency.

• Fix dependency scope and version compatibility
  The compile configuration is deprecated in newer Gradle versions; switch to implementation instead. Also, double-check that your liquibase-hibernate5 version matches your JHipster app’s Liquibase core version. For example, if JHipster uses Liquibase 4.x, the 3.6 hibernate extension will be incompatible. Update your build.gradle line to something like:

  implementation group: 'org.liquibase.ext', name: 'liquibase-hibernate5', version: '4.22.0'
  

  (Match the version to your project’s Liquibase core version—check your gradle.properties or dependency tree for that.)

• Add the dependency to Liquibase’s runtime classpath
  Sometimes adding the dependency to the general project scope isn’t enough for Liquibase tasks. Explicitly include it in the Liquibase task configuration in build.gradle:

  liquibase {
      activities {
          main {
              // Your existing changeLog, url, username, password config here
          }
      }
      dependencies {
          liquibaseRuntime 'org.liquibase.ext:liquibase-hibernate5:3.6' // Or your compatible version
      }
  }
  

• Clean Gradle’s cache and rebuild
  Corrupted cached dependencies can cause weird issues. Run these commands to reset:

  ./gradlew clean
  ./gradlew build --refresh-dependencies
  

  Then try ./gradlew liquibaseClearChecksums again.

• Verify your Liquibase configuration
  Double-check your application.yml/application.properties to make sure:

  • The Liquibase changeLog path is correct (usually src/main/resources/config/liquibase/master.xml)
  • Your database connection details are accurate (url, username, password)
  • No typos or formatting errors in your changeLog files that might be causing Liquibase to fail before it even gets to checksums.

• Dig into the error log details
  If none of the above works, share the full error stack trace! The exact error message (like "class not found", "database connection failed", or "invalid changeLog") will point us directly to the root cause—whether it’s a missing class, incompatible versions, or a broken change set.

内容的提问来源于stack exchange，提问作者James Freitas