Hello sorry for noob question, I want to apply `gradle-dependency-lock-plugin` at `gradle 5.4.1` But...

# gradle

[davidasync]

Hello sorry for noob question,
I want to apply gradle-dependency-lock-plugin at gradle 5.4.1
But got this error (check the thread)
Anybody familiar with this error ?

[davidasync]

Here's the error

* What went wrong:
Execution failed for task ':generateGlobalLock'.
> Could not resolve all dependencies for configuration ':detachedConfiguration1'.
   > Could not resolve project :common-cache.
     Required by:
         project :
      > Project : declares a dependency from configuration 'detachedConfiguration1' to configuration 'archives' which is not declared in the descriptor for com.accom:common-cache:1.1.0.

[davidasync]

and here's the build.gradle at root project

buildscript {
  repositories {
    maven {
      url "<https://maven-central-asia.storage-download.googleapis.com/repos/central/data>"
    }

    maven {
      url "<https://plugins.gradle.org/m2/>"
    }

    mavenCentral()
    jcenter()
    mavenLocal()
  }
  dependencies 
    classpath "com.netflix.nebula:gradle-dependency-lock-plugin:7.5.0"
  }
}

apply plugin: "nebula.dependency-lock"

wrapper {
  gradleVersion = '5.4.1'
  distributionType = "bin"
}

subprojects {
  apply plugin: 'java-library'
apply plugin: "nebula.dependency-lock"

  sourceCompatibility = 1.7
  targetCompatibility = 1.7
  
  repositories {
    maven {
      url "<https://maven-central-asia.storage-download.googleapis.com/repos/central/data>"
    }

    maven {
      url "<https://plugins.gradle.org/m2/>"
    }

    mavenCentral()
    jcenter()
    mavenLocal()
  }
}

[danny]

Does regular lock generation work? (i.e. generateLock)

[danny]

Could be a global locking bug - it's deprecated and we don't really use it here anymore

[danny]

If you need alignment of dependencies, you're better off using a common dependencies project that's depended on by the other projects

[danny]

I work with Martin @ Netflix, long time Nebula maintainer