如果檢測到不適當的依賴關係，則會造成Gradle構建失敗？

Question

使用Gradle時，我想確保在大型項目中進行適當的依賴關係管理，以便模塊A不能依賴於模塊B（即使是間接的）。我會如何去做這件事？

Answer 1

您可以分析所有依賴關係，並在發現不合適的情況時拋出異常。下面是它會爲一個特定的依賴性類路徑代碼：

apply plugin: 'java' 
repositories { 
    mavenCentral() 
} 

// This is just to have some dependencies on the classpath. 

dependencies { 
    compile 'org.springframework.boot:spring-boot-starter:1.5.1.RELEASE' 
    compile "org.webjars:webjars-locator:+" 
} 

// run this task to analyze all deps 

task checkDeps { 
    doLast { 
     // this closure simply prints a given dependency and throws an exception if slf4j-api is found 
     def failIfBad = { dep -> 
      println "CHECKING: $dep.module.id.group:$dep.module.id.name" 
      if (dep.module.id.name == 'slf4j-api') { 
       throw new GradleException("$dep.module.id.group:$dep.module.id.name on classpath!") 
      } 
     } 
     // this is a closure with recursion that calls the above failCheck on all children and their children 
     def checkChildren 
     checkChildren = { dep -> 
      if (dep.children.size() != 0) { 
       dep.children.each { child -> 
        failIfBad(child) 
        checkChildren(child) 
       } 
      } 
     } 
     // this is how you get all dependencies in the compile scope, iterate on the first level deps and then their children 
     configurations.compile.resolvedConfiguration.firstLevelModuleDependencies.each { firstLevelDep -> 
      failIfBad(firstLevelDep); 
      checkChildren(firstLevelDep); 
     } 
    } 
} 

整個代碼很可能進行優化，更復雜的規則是必要的，但它應該給你所需要的上手。