5.7.3 Debugging Resolution 2.4.4

See the light - agile, industrial strength, rapid web application development made easy

(Quick Reference) # 5.7.3 Debugging Resolution - Reference Documentation Authors: Graeme Rocher, Peter Ledbrook, Marc Palmer, Jeff Brown, Luke Daley, Burt Beckwith, Lari Hotari Version: 2.4.4 ## 5.7.3 Debugging Resolution If you are having trouble getting a dependency to resolve you can enable more verbose debugging from the underlying engine using the `log` method:
    // log level of the Aether or Ivy resolver, either 'error', 'warn',
    // 'info', 'debug' or 'verbose'
    log "warn"
A common issue is that the checksums for a dependency don't match the associated JAR file, and so Ivy rejects the dependency. This helps ensure that the dependencies are valid. But for a variety of reasons some dependencies simply don't have valid checksums in the repositories, even if they are valid JARs. To get round this, you can disable Ivy's dependency checks like so:
    grails.project.dependency.resolution = {
        …
        log "warn"
        checksums false
        …
    }
This is a global setting, so only use it if you have to. | Quick Reference (hide)